My Amazon author page!!!!
The reality that we wake up to. Things are complex. Sometimes things are doubly complex for no reason other than they simply don’t fit together.
For example, if your project is struggling you need to examine why. That is normal. You do a root cause analysis and determine it is a single person.
- Sometimes that person lives in an ego tower and can’t be bothered with your project. (it isn’t there project – it should have been there project ask them and they will tell you).
- Sometimes your project is off to a rocky start because it is simply harder than expected.
- Sometimes it was never on the rails and getting it on the rails will take more energy than you have.
In SDLC discussions we always talk about the lifecycle of software. We talk about the lifecycle of projects as well in a project. But sometimes we forget that a project may fail on the surface but in the end make the changes needed for the organization to move forward.
So the question that is rattling around inside my roomy expanded (and mostly empty head) is the concept of the lifecycle of an organization.
Enterprise architects spend time building a framework for an organization. They consider the requirements, the deployed solutions and the best way to solve a problem. For example they may say the best way to create a PDF file in an organization is to use EZPDF (a printing device) or possibly Adobe or event just save as a PDF in office. They tailor this guidance to what the organization has, needs and in the end wants.
The question I have is how do you move an organization forward? Its easy to upgrade a technical workforce (software is here, license is here have fun). Its harder to take a workforce that isn’t technical and move them quickly – and you also have to consider the what of the migration. if everyone stops what they are doing to upgrade there is a cost for that.
What is the lifecycle of technology in an organization?