change management plan template[1]

8/12/2019 Change Management Plan Template[1]

1/7

PROJECTCHANGEMANAGEMENTPLANTEMPLATE

This Project Change Management Template is free for you to copy and use on your projectand within your organization. We hope that you find this template useful and

welcome your comments. Public distribution of this document is only permitted

from the Project Management Docs official website at:www.ProjectManagementDocs.com

CHANGEMANAGEMENTPLAN

COMPANYNAME

STREETADDRESS

CITY, STATEZIPCODE

DATE
http://www.projectmanagementdocs.com/http://www.projectmanagementdocs.com/http://www.projectmanagementdocs.com/http://www.projectmanagementdocs.com/http://www.projectmanagementdocs.com/http://www.projectmanagementdocs.com/http://www.projectmanagementdocs.com/http://www.projectmanagementdocs.com/http://www.projectmanagementdocs.com/http://www.projectmanagementdocs.com/http://www.projectmanagementdocs.com/http://www.projectmanagementdocs.com/http://www.projectmanagementdocs.com/http://www.projectmanagementdocs.com/


2/7

Change Management Plan Template

!P"#$e%tManagementD#%&!%#m

TA'LEO(CONTENTS!T"#D$CT#!.................................................................................................................................%

C&'!()M'!'()M)!T'PP"#'C&................................................................................................%D)*!T#!+#*C&'!().................................................................................................................%

C&'!()C#!T"#,-#'"D.............................................................................................................."#,)+'!D")+P#!+-,T)+........................................................................................................./

C&'!()C#!T"#,P"#C)++.........................................................................................................../

0
http://www.projectmanagementdocs.com/http://www.projectmanagementdocs.com/


3/7



INTROD)CTIONChange Management is an important part of any project. Changes must be 1etted and managed

to ensure that they are within the scope of the project and are communicated to all sta2eholders if

they are appro1ed. The process for submitting3 re1iewing3 and appro1ing changes must also becommunicated to all sta2eholders in order to properly set e4pectations. f changes are allowed to

be submitted or are implemented in and unorganized way3 any project is sure to fail. 'll projectsmust include a Change Management Plan as part of the o1erall Project Plan.

The Change Management Plan was created for the n1entory +er1ices 5+6 Project in order to set

e4pectations on how the approach to changes will be managed3 what defines a change3 thepurpose and role of the change control board3 and the o1erall change management process. 'll

sta2eholders will be e4pected to submit or re7uest changes to the + Project in accordance with

this Change Management Plan and all re7uests and submissions will follow the process detailedherein.

CHANGEMANAGEMENTAPPROACHThis section describes the approach the organization will use for managing change throughout

the project. Throughout a project8s lifecycle there may be 1ery few or 1ery many submitted

changes. The approach ta2en to manage these changes must be consistent and repeatable inorder to pro1ide a 7uality change management plan and process.

The Change Management approach for the + Project will ensure that all proposed changes are

defined3 re1iewed3 and agreed upon so they can be properly implemented and communicated toall sta2eholders. This approach will also ensure that only changes within the scope of this

project are appro1ed and implemented.

The Change Management approach is not to be confused with the Change Management Process

which will be detailed later in this plan. The Change Management approach consists of three

areas:

)nsure changes are within scope and beneficial to the project

Determine how the change will be implemented

Manage the change as it is implemented

The Change Management process has been designed to ma2e sure this approach is followed for

all changes. -y using this approach methodology3 the + Project Team will pre1ent unnecessary

change from occurring and focus its resources only on beneficial changes within the project

scope.

DE(INITIONSO(CHANGEThis section defines the different types of changes that may be re7uested and considered for theproject. These changes may include schedule change3 budget change3 scope change3 or project

document changes. Most changes will impact at least one of these areas and it is important to

consider these impacts and how they will affect the project.

%


4/7



There are se1eral types of changes which may be re7uested and considered for the + Project.

Depending on the e4tent and type of proposed changes3 changes project documentation and thecommunication of these changes will be re7uired to include any appro1ed changes into the

project plan and ensure all sta2eholders are notified. Types of changes include:

+cheduling Changes: changes which will impact the appro1ed project schedule. These

changes may re7uire fast trac2ing3 crashing3 or re9baselining the schedule depending on

the significance of the impact.

-udget Changes: changes which will impact the appro1ed project budget. These changes

may re7uire re7uesting additional funding3 releasing funding which would no longer bere7uired3 or adding to project or management reser1es. May re7uire changes to the cost

baseline.

+cope Changes: changes which are necessary and impact the project8s scope which may

be the result of unforeseen re7uirements which were not initially planned for. Thesechanges may also impact budget and schedule. These changes may re7uire re1ision to

W-+3 project scope statement3 and other project documentation as necessary.

The project manager must ensure that any appro1ed changes are communicated to the project

sta2eholders. 'dditionally3 as changes are appro1ed3 the project manager must ensure that thechanges are captured in the project documentation where necessary. These document updates

must then be communicated to the project team and sta2eholders as well.

CHANGECONTROL'OARDThis section describes the Change Control -oard3 the purpose of the board3 and the members and

their roles on the board. The change control board is the appro1al authority for all proposedproject changes. f a change is not appro1ed by the control board then it will not be implementedwith the project. The size and function of change control boards may 1ary depending on the

organization but their purpose and the roles and responsibilities are consistent.

The Change Control -oard 5CC-6 is the appro1al authority for all proposed change re7uests

pertaining to the + Project. The purpose of the CC- is to re1iew all change re7uests3 determine

their impacts on the project ris23 scope3 cost3 and schedule3 and to appro1e or deny each changere7uest. The following chart pro1ides a list of the CC- members for the + Project:

Name P#&*t*#n CC' R#le

'. +mith + Project +ponsor CC- Chair T. White + Project Manager CC- Member

-. -rown + Project Technical ,ead CC- Co9Chair

. ones + Project #perations ,ead CC- Member

's change re7uests are submitted to the + Project Manager by the project team;sta2eholders3 the

Project Manager will log the re7uests in the change log and the CC- will con1ene e1ery other

*riday to re1iew all change re7uests. *or a change re7uest to be appro1ed3 all CC- members


5/7



must 1ote in fa1or. n the e1ent more information is needed for a particular change re7uest3 the

re7uest will be deferred and sent bac2 to the re7uestor for more information or clarification. f a

change is deemed critical3 an ad hoc CC- meeting can be called in order to re1iew the changeprior to the ne4t scheduled bi9wee2ly CC- meeting.

ROLESANDRESPONSI'ILITIESThis section describes the roles and responsibilities of project team members in regards to the

change management process. t is important that e1eryone understands these roles and

responsibilities as they wor2 through the change management process. These roles and

responsibilities must be communicated as part of the change management plan to all projectsta2eholders.

The following are the roles and responsibilities for all change management efforts related to the+ Project:

Project +ponsor:

'ppro1e all changes to budget;funding allocations

'ppro1e all changes to schedule baseline

'ppro1e any changes in project scope

Chair the CC-

Project Manager:

"ecei1e and log all change re7uests from project sta2eholders

Conduct preliminary ris23 cost3 schedule3 scope analysis of change prior to CC-

+ee2 clarification from change re7uestors on any open issues or concerns

Ma2e documentation re1isions;edits as necessary for all appro1ed changes

Participate on CC-

Project Team;+ta2eholders:

+ubmit all change re7uests on standard organizational change re7uest forms

Pro1ide all applicable information and detail on change re7uest forms

-e prepared to address 7uestions regarding any submitted change re7uests

Pro1ide feedbac2 as necessary on impact of proposed changes

CHANGECONTROLPROCESSThis section should describe the change control process from beginning to end. Typically3 achange control process should be an organizational standard and repeatable. This process is the

tool which is used to ensure adherence to the organization8s change management approach whichwas discussed in an earlier section. -y following all of the steps3 the project team can

successfully incorporate appro1ed changes3 communicate the changes3 and update project

documentation.

/


6/7



The Change Control Process for the + Project will follow the organizational standard change

process for all projects. The project manager has o1erall responsibility for e4ecuting the change

management process for each change re7uest.

06 dentify the need for a change 5+ta2eholders6 < Change re7uestor will submit a completed

change re7uest form to the project manager.%6 ,og change in the change re7uest register 5Project Manager6 < The project manager will

2eep a log of all submitted change re7uests throughout the project8s lifecycle.

6 )1aluate the change 5Project Manager3 Team3 "e7uestor6 < The project manager will

conduct a preliminary analysis on the impact of the change to ris23 cost3 schedule3 andscope and see2 clarification from team members and the change re7uestor.

/6 +ubmit change re7uest to CC- 5Project Manager6 < The project manager will submit the

change re7uest3 as well as the preliminary analysis3 to the CC- for re1iew.=6 #btain Decision on change re7uest 5CC-6 < The CC- will discuss the proposed change

and decide whether or not it will be appro1ed based on all submitted information.

>6 mplement change 5Project Manager6 < f a change is appro1ed by the CC-3 the projectmanager will update and re9baseline project documentation as necessary.

=


7/7



SPONSORACCEPTANCE

'ppro1ed by the Project +ponsor:

??????????????????????????????????????????? Date:????????????????????

@Project +ponsorA

@Project +ponsor TitleA

This free Project Change Management Plan Template is brought to you by www.ProjectManagementDocs.com

>
http://www.projectmanagementdocs.com/http://www.projectmanagementdocs.com/http://www.projectmanagementdocs.com/http://www.projectmanagementdocs.com/

change management plan template[1]

Documents