Change Management Free Sample

8/3/2019 Change Management Free Sample

1/12

Prepared By: Your Name

Document ID: Your ID Number

Revision: Your Revision

Date: Your Release

Date

Your Logo

Your OrganizationName

Your Project Name

Change Management Plan


2/12

Your Organization NameYour Project Name (replace with yourlogo)


Proprietary Notice

This document template is the property of ITProjectTemplates.com, which retains fullcopyright protection. The template may not be reproduced for resale.

This document template is released for the sole use of the purchasing client and their

delegates to modify for their own environment. It may be copied or distributed as

required within the purchasers organization only.

Disclaimer

This content of this document is based on the input of consultants, IT practitioners, and

subject matter experts whose expertise draws on learning and work experience from

many knowledge sources, both public and proprietary. Any resemblance to proprietary

work is purely coincidental.

Knowledge sources, both public and proprietary, may be cited from time to time as a

reference to the reader for independent research. These written references in no way

imply an endorsement of, or an association with, the cited reference.

Because this document is intended to be modified by the user, ITProjectTemplates.commakes no representation or warranty, either expressed or implied, with respect to the

sufficiency, accuracy, or utility of the document contents as completed by the user and

shall not be held liable for any damages incurred as a result of its use. The user

assumes full responsibility for project progress, completion and success.

Version: 0.1i


3/12

Your Organization Name(replace with your logo)

Your Project Name


Revision History

Version # Release Notes Issue Date

1.0 Initial Draft

Approval Signatures

Project Sponsor: Name Signature: _____________________

Project Manager: Name Signature: _____________________

Client Representative: Name Signature: _____________________

Quality Assurance: Name Signature: _____________________

Author: Name Signature: _____________________

iiVersion: 0.1


4/12



Instructions to the Author of this Document

Text in light blue italics, such as this paragraph, contains instructions and informationthat is intended to give you guidance on what to insert as content. It is not meant to be

part of the content itself. Delete the italicized lines before submitting the deliverable asfinal. Non-italicized text may be used verbatim at your discretion.

The deliverable author is to complete each section with the required information, asinstructed in the italicized text.

The cover page graphics, color motifs, and header and footer layouts are provided forconvenience; they are fully editable. It is recommended that you insert your logo, if

you have one, on the cover page where indicated. Also, it is recommended that youreplace our ITProjectTemplates graphic on the page headers with your own, or deletethe insertion.

Remove this page before submitting your final version of this deliverable.

Version: 0.1iii


5/12


Your Project Name


Table of Contents

Table of Contents.......................................iv

Introduction

1.1 Purpose...........................................................................................................................................5

1.2 Audience..........................................................................................................................................5

Change Management Overview

1.3 Change Management Approach......................................................................................................6

1.4 Change Management Cycle............................................................................................................6

1.5 Sources of Change..........................................................................................................................7

1.6 Roles and Responsibilities...............................................................................................................8

Change Management Procedures

1.7 Raise Change Request....................................................................................................................9

1.8 Asses Change Request...................................................................................................................9

1.9 Approve/Reject Change Request.....................................................................................................9

1.10 Implement Change.........................................................................................................................9

1.11 Close Change Request................................................................................................................10

Scope Change Management

1.12 Scope Change Categories...........................................................................................................11

ivVersion: 0.1


6/12



Introduction

1.1 Purpose

The purpose of this Change Management Plan is to set out the methods andprocedures to handle all changes affecting this projects:

Resources, costs, and timing as set out in the Project Plan

Deliverable, product and process Quality

Changes in ProductScope are drawn from the sources identified in section 2.3 andfollow the specified Change Request path through Change Management. Suchchanges also affect Project Scope, but are typically value-added and usually result

in an increase in scope.

Changes in ProjectScope are drawn from problems, issues, or executive decisionsinvolving key project dimensions, specifically time, cost, and/or quality. Suchchanges usually result in a decrease in Scope to accommodate changes in the

projects duration, budget, or quality demands.

1.2 Audience

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

Version: 0.15


7/12


Your Project Name


Change Management Overview

The following sub-sections contain boilerplate text. Use it as is, or modify it to suit yourproject situation.

1.3 Change Management Approach

This Change Management Plan employs an industry standard cyclical approach to:

Ensure standardized methods, processes and procedures are used for allproject changes

Facilitate efficient and prompt handling of all changes

Maintain a proper balance between the benefits of change and the detrimentalimpact of change on the Project Plan.

1.4 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 diagram on the next page represents the flow of change management events.

6Version: 0.1


8/12



Raise CR

Assess CR

Implement

Change

Accept CR?

Large CR?

Old Plan

More $

Yes

No

No

Yes

Close

New Plan

1.5 Sources of Change

All project changes must enter the Change Management cycle in the format of aChange Request. Legitimate changes to the product/project 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

Version: 0.17


9/12


Your Project Name


1.6 Roles and Responsibilities

The following list outlines the key responsibilities of personnel involved in theChange Management process:

Project Manager - assigned full responsibility for facilitating or executing thechange 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 againstexisting baseline

Configuration Manager/Change Manager accept, log and track CRs

Change Advisory Board comprised of Sponsor, Technical and Userrepresentatives, responsible for accepting or rejecting CR implementation

8Version: 0.1


10/12



Change Management Procedures

The following sub-sections contain boilerplate text. Use it as is, or modify it to suit your

project situation.

1.7 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 ChangeAdvisory Board or Project Board. This constitutes the initial informal changecommunication. At this point, the project authority may direct the initiator to preparea Change Request, or that duty may be delegated to the Project Manager or ChangeManager (if one exists for the project).

Once the details of the change have been recorded on a Change Request form, it issubmitted to the Configuration Manager or Change Manager to log into the ChangeLog.

1.8 Asses Change Request

The Change Request is escalated to the project core team for evaluation. A highlevel assessment is first performed by the Project Manager to determine if the CR isof sufficient magnitude to require independent funding for detailed assessment. Ifso, the Project Manager requests additional funding to carry out the extraassessment tasks.

The CR is assessed for its impact on the project plan (resources, costs andschedule) by the Project Manager and Project Coordinator. A separate timeline isbuilt 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 theProject Board members (technical and user representatives).

1.9 Approve/Reject Change Request

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

1.10Implement Change

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

Version: 0.19


11/12


Your Project Name


1.11Close Change Request

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

10Version: 0.1


12/12



Scope Change Management

1.12Scope Change Categories

and more detail follows. See the Change Management Plan under the ProjectManagement document listings for the complete deliverable.

Version: 0.111

Change Management Free Sample

Documents

Transcript of Change Management Free Sample