This change management plan outlines the process for managing changes to the Project Management Improvement, Phase 3 project. It defines the project constraints, items subject to change management, roles and responsibilities, and the five step change management process of submittal and logging, evaluation, decision, integration, and communication. The budgetary impact of changes is estimated to be between $250-$500, with approximately 5 change requests requiring 10-15 hours to evaluate and manage.

1. Change Management Plan
Project Name:
Project Management Improvement,
Phase 3
Example
Disclaimer: This example is based on the Project Management Improvement project, but is not
necessarily an actual case for that project.
Prepared By: Person A
Title: Project Management Improvement, Phase 3
Version No: 1.0

2. Document Change Control
The following is the document control for revisions to this document.
Version Date of
Author(s) Brief Description of Change
Number Issue
1.0 12/1/06 Person A Initial plan
Definition
The following are definitions of terms, abbreviations and acronyms used in this document.
Term Definition
DoIT Division of Information Technology
PMA Project Management Advisor
3.3.4 Example – Change Management Plan, v2.0 Page i

3. Table Of Contents
1. PROJECT CONSTRAINTS .............................................................................. 1
2. CHANGE MANAGEMENT GUIDELINES AND PURVIEW. ............................. 1
3. ESTIMATE OF CHANGE VOLUME ................................................................. 1
4. ROLES AND RESPONSIBILITIES ................................................................... 1
5. THE CHANGE MANAGEMENT PROCESS ..................................................... 2
6. TOOLS ............................................................................................................. 3
3.3.4 Example –Change Management Plan v2.0 Page ii

4. 1. Project constraints
We acknowledge the following project constraints:
• Fixed budget set at $73,360
• Scope is firm for completion of basic framework components, otherwise constrained by
cost.
• Phase 3 deadline is flexible, provided project is completed by 6/30/07
• Quality is important, but reviews will be constrained to meet budget constraints.
2. Change management guidelines and purview.
The following items will be subject to change management.
Primary deliverables
• Framework components
• Project Management Advisor (PMA) components
Secondary deliverables
• Budget
• Schedule
• Scope
The project team has latitude to interpret requirements in the following areas:
• Specific framework content
• Task assignments
• Quality review specifics
3. Estimate of change volume
The budgetary impact of change in this project is expected to fall within the range of $250 to
$500. We assume the number of change requests will be roughly 5. We estimate change
evaluation and management to require 10-15 hours.
4. Roles and responsibilities
The project manager will serve as change manager and lead change evaluator.
Responsibilities include:
• receive and log change requests
• perform the timely and adequate evaluation of changes in terms of their impacts on
project deliverables and constraints
• outline options and recommend courses of action and priorities for changes
• track and facilitate timely decisions on changes
• incorporate changes into the appropriate project documents
3.3.4 Example –Change Management Plan v2.0 Page 1

5. • communicate changes to the project team and others as the communication plan below
dictates
The change requestor, who is any key stakeholder, may submit project change requests
following the submittal process indicated below.
The project sponsors will serve as change evaluators and change decision makers .
Responsibilities include:
• evaluate options and recommended courses of action for these changes
• approve or reject changes
5. The change management process
For each change the following process will be followed. Note that logging occurs at various
points in the process, e.g. after evaluation and after the decision, not shown in this diagram.
5.1 Submittal and Logging: Change requests will be submitted using the change request form
referenced below. A change resulting from a realized risk or issue will be documented through a
change request form. The change manager will scan risks and issues for likely changes every
month.
5.2 Evaluation: The lead change evaluator will evaluate all change request.
Unless otherwise noted, change requests will be evaluated within 15 days of submission.
5.3 Decision: Unless otherwise noted, changes will be approved, rejected, or parked within 15
days of submission to the change decision maker. The decision maker may also request further
evaluation.
5.4 Integration: The change manager will update project documentation for significant changes
only. A running summary of changes will be posted to the project change log within My
Webspace.
3.3.4 Example –Change Management Plan v2.0 Page 2

6. 5.5 Communication: The project team will be notified of changes as they are approved at the
next project team meeting. Other stakeholders will be notified of changes in the monthly project
status report.
6. Tools
Change request form
See attached change request template.
Change log
See attached change log template.
3.3.4 Example –Change Management Plan v2.0 Page 3