Scribd
Upload
220 views

Your Organization Name Your Project Name Change Management Plan

This document outlines a change management plan for a project that includes: 1) An overview of the change management approach and cycle used, which employs a standardized cyclical process to efficiently handle all changes. 2) Details on the roles and responsibilities of those involved in the change management process, including the project manager and change advisory board. 3) The procedures for raising a change request, assessing its impact, approving or rejecting it, implementing approved changes, and closing out change requests.

Uploaded by

tmujtaba
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
220 views

Your Organization Name Your Project Name Change Management Plan

This document outlines a change management plan for a project that includes: 1) An overview of the change management approach and cycle used, which employs a standardized cyclical process to efficiently handle all changes. 2) Details on the roles and responsibilities of those involved in the change management process, including the project manager and change advisory board. 3) The procedures for raising a change request, assessing its impact, approving or rejecting it, implementing approved changes, and closing out change requests.

Uploaded by

tmujtaba
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 12

Your Organization Name Your Project Name Change Management Plan

Prepared by: Version: Document #: Date:

Your Name Your Version Your Reference # Release Date

Project Name Change Management Plan

Proprietary Notice
This document is the property of IT-Project-Templates.com and contains an embedded digital signature verifying its ownership. This document is released for the sole use of authorized clients and their delegates and may not be copied or reproduced for resale.

Document #

Page i

Version 1.0

Project Name Change Management Plan

Approval Signatures

Project Sponsor: Project Manager: Client Representative: Quality Assurance: Author:

Name Name Name Name Name

Signature: _____________________ Signature: _____________________ Signature: _____________________ Signature: _____________________ Signature: _____________________

Document #

Page ii

Version 1.0

Project Name Change Management Plan

Revision History

Version # 1.0

Release Notes Initial Draft

Issue Date

Document #

Page iii

Version 1.0

Project Name Change Management Plan

Table of Contents
1. INTRODUCTION................................................................................................1
1.1. Purpose..............................................................................................................1 1.2. Audience.............................................................................................................1

2. CHANGE MANAGEMENT OVERVIEW............................................................2


2.1. Change Management Approach........................................................................2 2.2. Change Management Cycle...............................................................................2 2.3. Sources of Change.............................................................................................3 2.4. Roles and Responsibilities.................................................................................3

3. CHANGE MANAGEMENT PROCEDURES......................................................4


3.1.1. Raise Change Request........................................................................4 3.1.2. Asses Change Request........................................................................4 3.1.3. Approve/Reject Change Request.........................................................4 3.1.4. Implement Change...............................................................................4 3.1.5. Close Change Request........................................................................5

APPENDIX A CHANGE REQUEST..................................................................6 APPENDIX B CHANGE CONTROL LOG.........................................................7

Document #

Page iv

Version 1.0

Project Name Change Management Plan

1. INTRODUCTION
1.1. Purpose
The purpose of this Change Management Plan is to set out the methods and procedures to handle all changes affecting this projects: Resources, costs, and timing as set out in the Project Plan Deliverable, product and process Quality

1.2.

Audience
This Change Management Plan is intended for the Project Board, key stakeholders, and the core project team.

Document #

Page1

Version 1.0

Project Name Change Management Plan

2. CHANGE MANAGEMENT OVERVIEW


2.1. Change Management Approach
This Change Management Plan employs an industry standard cyclical approach to: Ensure standardized methods, processes and procedures are used for all project changes Facilitate efficient and prompt handling of all changes Maintain a proper balance between the benefits of change and the detrimental impact of change on the Project Plan.

2.2.

Change Management Cycle


The Change Management Cycle is comprised of the following events: Raise and record Change Request (CR) Assess impact and value of change Present assessment results and obtain approval Implement change and re-baseline plan Close CR

The following diagram represents the flow of change management events.

Document #

Page2

Version 1.0

Project Name Change Management Plan

2.3.

Sources of Change
All project changes must enter the Change Management cycle in the format of a Change Request. Legitimate changes may stem from: Responses to problems internal to the project Externally imposed requirements Change in business requirements or strategy Proactive changes to improve performance or benefit

2.4.

Roles and Responsibilities


The following list outlines the key responsibilities of personnel involved in the Change Management process: Project Manager - assigned full responsibility for facilitating or executing the change management process to officially provide new requirements, scope, schedule and resources Project Sponsor responsible for reviewing, authorizing and funding changes Project Coordinator assists with estimating and scheduling change against existing baseline Configuration Manager/Change Manager accept, log and track CRs Change Advisory Board comprised of Sponsor, Technical and User representatives, responsible for accepting or rejecting CR implementation

Document #

Page3

Version 1.0

Project Name Change Management Plan

3. CHANGE MANAGEMENT PROCEDURES


3.1.1. Raise Change Request
The change initiator communicates the details of the change to any project authority, such as the Project Manager, Project Sponsor, or any other member of the Change Advisory Board or Project Board. This constitutes the initial informal change communication. At this point, the project authority may direct the initiator to prepare a Change Request, or that duty may be delegated to the Project Manager or Change Manager (if one exists for the project). Once the details of the change have been recorded on a Change Request form, it is submitted to the Configuration Manager or Change Manager to log into the Change Log.

3.1.2. Asses Change Request


The Change Request is escalated to the project core team for evaluation. A high level assessment is first performed by the Project Manager to determine if the CR is of sufficient magnitude to require independent funding for detailed assessment. If so, the Project Manager requests additional funding to carry out the extra assessment tasks. The CR is assessed for its impact on the project plan (resourcing, costs and schedule) by the Project Manager and Project Coordinator. A separate timeline is built for later incorporation into the master plan, if and when the CR is approved. The Project Manager completes a brief Business Case with the assistance of the Project Board members (technical and user representatives).

3.1.3. Approve/Reject Change Request


The results of the CR assessment are presented to the Change Advisory Board and/or the Project Board. Based on the value judgement passed on the CR, it is accepted or rejected. If accepted, sign-off represents a new agreement on the updated Project Plan. The new timeline, Scope, costs and schedule are baselined.

3.1.4. Implement Change


The new work required by the change is undertaken and completed according to the new Project Plan. Success criteria or testing for the change are applied to the CR work. Completion is assessed at the appropriate milestone.

Document #

Page4

Version 1.0

Project Name Change Management Plan

3.1.5. Close Change Request


Following successful implementation and testing of the CR work, the Configuration Manager makes a closing entry in the Change Management Log.

Document #

Page5

Version 1.0

Project Name Change Management Plan

APPENDIX A CHANGE REQUEST


Change Request Form
CHANGE IDENTIFICATION SECTION Change Control # Short Title: Requested by: Name or Project/Program Date: Affected System(s): Supporting Materials Attached (yes/no)

Type of request (P, A, D, T): P=Plan/Sched Chg, A=Architecture Chg, D=Design Chg, T=Tech Chg Description of Change Request: Reason for Change:

EVALUATION SECTION Identify requirements, & products/deliverables changes: Identify plan changes: Total Hours: Description of risks: Risks associated with making and not making changes to system, project, and business: Recommendation: Evaluated by: DECISION APPROVAL SECTION Cancel __ Decision Approval Signatures: Sponsor: Technical/User Rep: Project Mgr: Postpone __ Reconsider on: ____________ Integrate into Project __ Date: Estimate of effort (hrs) :

Document #

Page6

Version 1.0

Project Name Change Management Plan

APPENDIX B CHANGE CONTROL LOG


CHANGE MANAGEMENT LOG YOUR PROJECT NAME Impact and Deliverables affected

No Issue date

Requestor

Title of request

Resp. Person

Compl Date

Status

Document #

Page7

Version 1.0

You might also like