Is Your Methodology Mature?
Over the past 10 years, the impatient “just get it done” attitude to projects has faded, making way for the evolution of a new mindset on project management. It is now generally understood that rushed projects are mismanaged projects that waste money and business opportunities. What used to be thought of as unnecessary administrative overhead is now considered not only necessary practice but good business. Consequently, project and project management methodologies have also continued to evolve and grow in usage. Creating a prescribed method for approaching projects within your organization has many advantages, but how mature does an organization need to be to adopt structured methodologies?
Executives want to know initiatives are being managed efficiently and effectively to drive business results, and they want it done consistently. They want to know that risk is being managed and demand transparency as proof that the project is heading toward the intended results. But to have transparency, the organization first needs consistent processes and common markers so that information can be rolled up in a useful way for measuring and reporting. Standards, frameworks and methodologies are implemented to generate consistency.
What's the difference between a framework, methodology or standard you ask? Good question. Ask 10 people and you will probably get 10
Please log in or sign up below to read the rest of the article.
|
"O, it is excellent To have a giant's strength! But it is tyrannous To use it like a giant." - William Shakespeare |




