First, this is not from me, but from my partner's experience working for couple of years developing an enterprise application. Hearing her complain everyday makes me pray to God that I would not get any enterprise app job :D.
She is developing a quite big finance enterprise app that is handled by multiple teams. Each team develop a certain part of the app that will communicate together as well as with other third party system. Each team has its own "Business" person as well as a "Technical Lead" person as well as a "Stakeholder". Yes, each team. In the upper hieararchy, there is another "Stackholder" with another "Technical Director".
Reading that I think you may already knew what's the problem. Too many heads. Time spent just grooming stories or gathering requirements, that may be changed in the next hour. Teams are not productive as every day they have to attend meetings, quickly turning into fighting arena between those "Management level" employees.
Too many manangement/business level arguments resulting in unclear planning and requirements. This will end up exhausting developers and teams. Imagine building a large mall constructing and deconstructing without knowing what the end result will be. Of course this will produce bad code, no documentation and low level of OWNERSHIP. Thus, a high cost low maintainable product are made.
I remember early years as Software Developers, I always have this sense of Ownership and pride of what I do, so does she. But I don't see that value in her lately.
So, yeah.. enterprise applications sometimes have this high level of challenges. Probably bad management? probably wrong company? I think in most companies the challenges are pretty similar.
First, this is not from me, but from my partner's experience working for couple of years developing an enterprise application. Hearing her complain everyday makes me pray to God that I would not get any enterprise app job :D.
She is developing a quite big finance enterprise app that is handled by multiple teams. Each team develop a certain part of the app that will communicate together as well as with other third party system. Each team has its own "Business" person as well as a "Technical Lead" person as well as a "Stakeholder". Yes, each team. In the upper hieararchy, there is another "Stackholder" with another "Technical Director".
Reading that I think you may already knew what's the problem. Too many heads. Time spent just grooming stories or gathering requirements, that may be changed in the next hour. Teams are not productive as every day they have to attend meetings, quickly turning into fighting arena between those "Management level" employees.
Too many manangement/business level arguments resulting in unclear planning and requirements. This will end up exhausting developers and teams. Imagine building a large mall constructing and deconstructing without knowing what the end result will be. Of course this will produce bad code, no documentation and low level of OWNERSHIP. Thus, a high cost low maintainable product are made.
I remember early years as Software Developers, I always have this sense of Ownership and pride of what I do, so does she. But I don't see that value in her lately.
So, yeah.. enterprise applications sometimes have this high level of challenges. Probably bad management? probably wrong company? I think in most companies the challenges are pretty similar.
What Application or Job are you doing?
I am a full stack web dev, I am doing several projects for my company now, mostly web+angular apps for OHS, Insurance, etc.
But in that enterprise application context, it is my wife who are developing an enterprise financial system that I can't tell the details.