Change Plan Template and Example

22,431 views

Published on

Published in: Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
22,431
On SlideShare
0
From Embeds
0
Number of Embeds
58
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Change Plan Template and Example

  1. 1. Change Management PlanProject Name:Project Management Improvement,Phase 3ExampleDisclaimer: This example is based on the Project Management Improvement project, but is notnecessarily an actual case for that project.Prepared By: Person ATitle: Project Management Improvement, Phase 3Version No: 1.0
  2. 2. Document Change ControlThe 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 planDefinitionThe following are definitions of terms, abbreviations and acronyms used in this document. Term Definition DoIT Division of Information Technology PMA Project Management Advisor3.3.4 Example – Change Management Plan, v2.0 Page i
  3. 3. Table Of Contents1. PROJECT CONSTRAINTS .............................................................................. 12. CHANGE MANAGEMENT GUIDELINES AND PURVIEW. ............................. 13. ESTIMATE OF CHANGE VOLUME ................................................................. 14. ROLES AND RESPONSIBILITIES ................................................................... 15. THE CHANGE MANAGEMENT PROCESS ..................................................... 26. TOOLS ............................................................................................................. 33.3.4 Example –Change Management Plan v2.0 Page ii
  4. 4. 1. Project constraintsWe 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) componentsSecondary deliverables • Budget • Schedule • ScopeThe project team has latitude to interpret requirements in the following areas: • Specific framework content • Task assignments • Quality review specifics3. Estimate of change volumeThe 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 changeevaluation and management to require 10-15 hours.4. Roles and responsibilitiesThe 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 documents3.3.4 Example –Change Management Plan v2.0 Page 1
  5. 5. • communicate changes to the project team and others as the communication plan below dictatesThe change requestor, who is any key stakeholder, may submit project change requestsfollowing 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 changes5. The change management processFor each change the following process will be followed. Note that logging occurs at variouspoints 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 formreferenced below. A change resulting from a realized risk or issue will be documented through achange request form. The change manager will scan risks and issues for likely changes everymonth.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 15days of submission to the change decision maker. The decision maker may also request furtherevaluation.5.4 Integration: The change manager will update project documentation for significant changesonly. A running summary of changes will be posted to the project change log within MyWebspace.3.3.4 Example –Change Management Plan v2.0 Page 2
  6. 6. 5.5 Communication: The project team will be notified of changes as they are approved at thenext project team meeting. Other stakeholders will be notified of changes in the monthly projectstatus report.6. ToolsChange request formSee attached change request template.Change logSee attached change log template.3.3.4 Example –Change Management Plan v2.0 Page 3

×