Mature Change?
If your experiences are like mine, it seems that as soon as a project begins, change follows. Most project managers think of changes to a project to be related to change requests that modify the scope of the deliverables. But changes to projects go far beyond mere scope changes.
Projects are composed of many moving parts and components, and the longer the project time horizon, the more likely one or more of these parts is going to change. And unlike change requests that can go through an approval process, many of the changes that impact projects the most happen without regard to or consideration of its impact upon the project. These changes are event driven and include changes in:
- Management
- Ownership
- Reorganization
- Stakeholders
- Key Operational Personnel
- Funding
- Business Strategies & Objectives
- Third-Party Resources
- Project Team Members
- Technologies
- Economy
- Competitive Landscape
- Regulations
- Disasters and more
A change in any one of the above project components could impact the scope, business case and even the viability of the project. No matter what the source of a material change, it is incumbent upon the project manager to evaluate the impact of the change on the project and it components. Therefore, it is important to have a project change management process in place that
Please log in or sign up below to read the rest of the article.
|
"I've always believed in the adage that the secret of eternal youth is arrested development." - Alice Roosevelt Longworth |




