4.1.0.1P Perform Integrated Change Control

(4.1.0.1P.P1)

Large projects should apply more diligence throughout the change management process. Change does not always happen neatly. In many cases, it may be hard to understand the nature of a change and the impact to the various aspects of the project. For example a small request can come into the project that results in a change to scope. The scope change request may lead to a request to increase schedule and budget. The request might impact the types of resources that are needed on the project and it might affect a vendor contract. The project manager needs to understand the nature of the change and how it might impact all other aspects of the project.

That is the purpose of Integrated Change Control, a high-level process that encompasses the more specific scope change, configuration change and general change management processes. Integrated change control includes the following activities.

  • Making sure there are baselines in place (scope, budget, schedule, etc.) so that it is more obvious that a change has occurred

  • Looking at the causes of change to see if the causes can be (or should be) eliminated. For instance, if you believe you are receiving too many scope change requests, it may reflect on a poor requirements gathering process.

  • Making sure no changes are implemented unless they have been approved.

  • Making sure there are processes in place to manage change. The level of formality of the approval process increases with the size of the project and the size of the potential change.

  • Making sure the entire project team, including the client, understands the change management processes and follows them.

  • Making sure the appropriate documentation is created and saved for each change.

  • Understanding how changes impact all related aspects of the project and making sure all of the appropriate documentation is updated.

  • Making sure that there is a person or body available to approve or reject all change requests.

  • Making sure all change requests are closed by either an acceptance of the change or rejection of the change.

  • Communicating changes and the impact on the project to the appropriate stakeholders.

Verify Scope (4.1.0.1P.P2)

 

Role

Defining the Work (Large Project)

1

Project Manager

Get the Project Charter approved.

See the 2.1T Define the Work / Techniques section for information on how to circulate the document and options for signifying approval.

2

Project Manager

Circulate approved Project Charter to all interested stakeholders.

After the approval process is complete, circulate copies of the approved Project Charter and Project Management Plan to all interested stakeholders, including the project team members.