Change Control Process

Purpose
The purpose of this document is to provide the project manager, sponsors, steering committee members and all
other stakeholders with the standard process for managing changes on the [project name] project.
Related Documents
The scope of the [project name] has been defined in the approved Project Charter dated [date]. The work
breakdown of the project and the timeline are detailed in the approved project plan dated [date].
Purpose and Objectives
The purpose of this change management procedure is to manage change requests so that approved changes will be
controlled, ensuring the project remains on schedule, within budget and provides the agreed deliverables.
The primar objectives of change management are to!
manage each change request from initiation through to closure"
process change requests based upon direction from the appropriate authorit"
communicate the impact of changes to appropriate personnel" and
allow small changes to be managed with a minimum of overhead.
Scope
The Change #anagement Process is the mechanism used to initiate, record, assess, approve and resolve project
changes. Project changes are needed when it is deemed necessar to change the scope, time or cost of one or more
previousl approved project deliverables. #ost changes will affect the budget and$or schedule of the project.
Policy
The use of the formal change management procedure will be required when an changes are discovered or
requested which impact previousl reviewed, approved and published project deliverables.
The documentation and tracking of all change requests will be managed using the defined procedure and facilitated
b the use of the change management log.
% multi&tiered approach will be used to approve change requests!
The Project #anager will make decisions to anal'e and decisions to proceed with changes if the changes
do not impact scope, budget or schedule or result in an increase in risk for the project.
Changes which do impact scope, budget or schedule will be forwarded to the (teering Committee for
review. The (teering Committee will advise the Project (ponsor.
)here the [functional owner] has the resources to absorb the impact of the change, the Project (ponsor will
make the final decision, based upon the information provided b the Project #anager and the input of the
(teering Committee. The Project (ponsor, the [advisor], and [advisor] will discuss requests that ma result
in a significant change in scope, schedule, and budget, i.e. the impact of the change cannot be covered b
[functional owner] resources. This group will advise the (teering Committee.
The (teering Committee will make the final decision based upon the information provided
*
.
+ecision #atri,
The following is a general guideline for the change management process. #ost changes will require a
subset of the steps listed.
Procedures
-ach request will be tracked from the time of presentation through!
*. .dentif /identif and document the required change0
1. 2alidate /verif the change is valid and requires management0
3. %nal'e /anal'e and record schedule, cost and effort impact of change0
4. Control /decide whether to e,ecute the change0
5. %ction /e,ecute decision, including revision to project plans if necessar0
6. Close /verif that action is complete and close change request0
Identify Change Request
Action Responsibility
1. Identify and record the issue (in [location]). Project Manager or Team Lead
1
Validate Change Request
Action Responsibility
2. Identify memer of the management team as the issue o!ner.
". #alidate change re$uest !ith %roject team memers as a%%ro%riate.
&. 'ssess and e(aluate change for necessity to %roject.
). *%date change re$uest !ith target date for com%letion of analysis.
Project Manager

naly!e Impact
Action Responsibility
+. Triage !, consultation of the Project -%onsor
.. Meet contract re$uirements for res%onding to /hange 0e$uests.
1. 'ssign resources to re(ie! the im%act of the change re$uest.
2. 3irect acti(ity to assess the sco%e4 cost and schedule im%act of the
change.
15. *%date change re$uest !ith im%act analysis and estimates in terms of
sco%e4 cost4 schedule and effort im%acts.
11. *%date change re$uest !ith target date for decision.
Project Manager

Control Change Request
Action Responsibility
12. Meet -igma contract re$uirements for res%onding to /hange 0e$uests.
1". 3etermine re$uired a%%ro(als and assign %riority to the change re$uest.
1&. If changes im%act sco%e4 udget or schedule %lace re$uest on agenda for
ne6t -teering /ommittee meeting.
1). If changes do not im%act sco%e4 udget or schedule decide !hether to
%roceed !ith the change.
Project Manager
1+. 0e(ie! and discuss analysis of change re$uest.
1.. 3e(elo% recommendation for the Project -%onsor.
-teering /ommittee
11. 3ecide !hether to %roceed !ith the change.
*7. If im%act of change cannot e asored y [functional o!ner]4 schedule
discussion !ith [ad(isor names].
Project -%onsor
25. 0e(ie! and discuss analysis of change re$uest.
21. If change re$uest should e escalated to -teering /ommittee4 %lace
re$uest on agenda for ne6t meeting (or email if re$uest is urgent).
22. 3e(elo% recommendation for the -teering /ommittee.
Project -%onsor4 [ad(isor names]
2". 0e(ie! and discuss analysis of change re$uest.
2&. 3ecide !hether to %roceed !ith the change.
-teering /ommittee
2). 7enerate a%%ro(al signature sheets for each outstanding change re$uest.
2+. *%date status of change re$uest !ith control decision.
Project -%onsor
ction Change Request
Action Responsibility
2.. 8egotiate contract changes.
21. 96ecute contract changes.
Project Manager4 Project -%onsor4
Technology 'c$uisition Manager
22. Incor%orate change re$uest into a%%ro%riate %lans and !or: %lan.
"5. *%date !or: %lan aseline for agreed changes.
Project Manager
Close Change Request
Action Responsibility
"1. /lose change re$uest..
"2. /ommunicate !or: %lan change to %roject team.
"". Monitor and re%ort %rogress against %roject %lan.
"&. /onfirm all u%dates ha(e een recorded and file all /hange 0e$uest
3ocuments.
Project Manager
3