VP/CIO PROJECT MANAGEMENT
Guideline: Change Management
Purpose: The purpose of change management is to identify the
process for requested changes to scope, schedule, and budget.
Last Modified Date:
October 31, 2011
All projects will have changes requested. Requested changes should always be addressed promptly.
Maintaining control over your change requests helps keep your project on track.
There are three main steps to the change management process and they are listed below. After each
step, there are questions to help you think through the issues.
1. Develop a method to identify changes.
a. Who can request changes?
b. How are changes requested?
c. Who receives change requests?
d. How will change requests be documented?
2. Review, assess, and document the impact of change requests. Approve or reject change
requests.
a. Who will review and assess the change requests for impact on the project? Are there
alternatives to the change request that should be considered?
b. How will you document the change request and its impact?
c. Who will approve or reject the change request?
d. Who will communicate the approval or rejection of the change request to the
stakeholders? How will it be communicated?
3. Implement approved change requests and adjust baselines where necessary.
a. Who will communicate when the approved change request is completed? How will it
be communicated?
b. How will this be documented?
c. If there is a scope, budget, or schedule change, who will update the scope, budget, or
schedule baselines as a result of the approved and implemented change?