Change Management PLAN Version VERSION HISTORY [Provide information on how the development and distribution of the Change Management Plan, up to the final point of approval, was controlled and tracked. Use the table below to provide the version number, the author implementing the version, the date of the version, the name of the person approving the version, the date that particular version was approved, and a brief description of the reason for creating the revised version.] Version#Implemented ByRevision DateApproved ByApproval DateReason1.0 UP Template Version: 11/30/06 Note to the Author [This document is a template of a Change Management Plan document for a project. The template includes instructions to the author, boilerplate text, and fields that should be replaced with the values specific to the project. When using this template for your project document, it is recommended that you follow these steps: TABLE OF CONTENTS 1 Introduction.. 5 1.1 Purpose of The Change Management Plan.. 5 2 Change management Process.. 5 2.1 Change Request Process Flow Requirements. 5 2.2 Change Request Form and Change Management Log. 6 2.3 Evaluating and Authorizing Change Requests. 6 2.3.1 Change Control Board. 7 3 Responsibilities.. 7 Appendix A: Change Management Plan Approval.. 8 Appendix B: References.. 9 Appendix C: Key Terms.. 10 Appendix D: Change Request Form Example.. 11 Appendix E: Change Management Log Template.. 12 1 Introduction 1.1 Purpose of The Change Management Plan [Provide the purpose of the Change Management Plan. This document should be tailored to fit the particular project needs.] The Change Management Plan documents and tacks the necessary information required to effectively manage project change from project inception to delivery. The Change Management Plan is created during the Planning Phase of the project. Its intended audience is the project manager, project team, project sponsor and any senior leaders whose support is needed to carry out the plan. 2 Change management Process The Change Management process establishes an orderly and effective procedure for tracking the submission, coordination, review, evaluation, categorization, and approval for release of all changes to the project’s baselines. 2.1 Change Request Process Flow Requirements [Outline the project team’s agreed upon change request (CR) process flow. The following outlines a generic change request process flow.] StepDescriptionGenerate CRA submitter completes a CR Form and sends the completed form to the Change ManagerLog CR StatusThe Change Manager enters the CR into the CR Log. The CR’s status is updated throughout the CR process as needed.Evaluate CRProject personnel review the CR and provide an estimated level of effort to process, and develop a proposed solution for the suggested changeAuthorizeApproval to move forward with incorporating the suggested change into the project/productImplementIf approved, make the necessary adjustments to carry out the requested change and communicate CR status to the submitter and other stakeholders 2.2 Change Request Form and Change Management Log [List and define the data elements the project team needs to include on the Change Request Form and in the Change Management Log. Examples of these are provided in Appendix D and Appendix E. At a minimum, the following data should be included on the project’s Change Request Form and Change Management Log.] ElementDescriptionDateThe date the CR was createdCR#Assigned by the Change ManagerTitleA brief description of the change requestDescriptionDescription of the desired change, the impact, or benefits of a change should also be describedSubmitterName of the person completing the CR Form and who can answer questions regarding the suggested changePhonePhone number of the submitterE-MailEmail of the submitterProductThe product that the suggested change is forVersionThe product version that the suggested change is forPriorityA code that provides a recommended categorization of the urgency of the requested change (High, Medium, Low) 2.3 Evaluating and Authorizing Change Requests [In order to evaluate and prioritize a change request, the “priority” and “type” of the change are taken into consideration. Use the first and second tables below to list and define the “priority” and “type” data elements that are applicable for the project. The third table provides examples of commonly used project status types. The list of elements is at the discretion of the project manager.] Change requests are evaluated using the following priority criteria: PriorityDescriptionHighMediumLow Change requests are evaluated and assigned one or more of the following change types: TypeDescriptionScopeChange affecting scopeTimeChange affecting timeDurationChange affecting durationCostChange affecting costResourcesChange affecting resourcesDeliverablesChange affecting deliverablesProductChange affecting productProcessesChange affecting processQualityChange affecting quality Change requests are evaluated and assigned one of the following status types: StatusDescriptionOpenEntered/Open but not yet approved or assignedWork in ProgressCR approved, assigned, and work is progressingIn ReviewCR work is completed and in final review prior to testingTestingCR work has been reviewed and is being testedClosedCR work is complete, has passed all tests, and updates have been released. 2.3.1 Change Control Board [A Change Control Board (CCB) is a formally constituted group of stakeholders responsible for approving or rejecting changes to the project baselines. This group may meet on a predefined schedule or on an as needed basis. The table below provides a brief description of personnel acting as the Change Control Board (CCB) and their role/level of authority within that group.] RoleNameContactDescription [Insert Role][Insert Name][Insert Contact #][Insert Role Description] 3 Responsibilities [Provide a brief description of persons responsible for each step of the change management process for the project.] RoleNameContactDescriptionProject Manager Change Manager [Insert Role][Insert Name][Insert Contact #][Insert Role Description] Appendix A: Change Management Plan Approval The undersigned acknowledge they have reviewed the Change Management Plan and agree with the approach it presents. Changes to this Change Management Plan will be coordinated with and approved by the undersigned or their designated representatives. [List the individuals whose signatures are desired. Examples of such individuals are Business Steward, Project Manager or Project Sponsor. Add additional lines for signature as necessary. Although signatures are desired, they are not always required to move forward with the practices outlined within this document.] Signature: Date: Print Name: Title: Role: Signature: Date: Print Name: Title: Role: Signature: Date: Print Name: Title: Role: Appendix B: References [Insert the name, version number, description, and physical location of any documents referenced in this document. Add rows to the table as necessary.] The following table summarizes the documents referenced in this document. Document Name and VersionDescriptionLocation[Provide description of the document] Appendix C: Key Terms [Insert terms and definitions used in this document. Add rows to the table as necessary. Follow the link below to for definitions of project management terms and acronyms used in this and other documents. http://www2.cdc.gov/cdcup/library/other/help.htm The following table provides definitions for terms relevant to this document. TermDefinition[Insert Term][Provide definition of the term used in this document.][Insert Term][Provide definition of the term used in this document.][Insert Term][Provide definition of the term used in this document.] Appendix D: Change Request Form Example The example Change Request From attached below can be used to submit changes during the life of the project. Appendix E: Change Management Log Template The detailed Change Management Log template attached below can be used to track and manage requested changes during the life of the project. Change Management PLAN Version VERSION HISTORY [Provide information on how the development and distribution of the Change Management Plan, up to the final point of approval, was controlled and tracked. Use the table below to provide the version number, the author implementing the version, the date of the version, the name of the person approving the version, the date that particular version was approved, and a brief description of the reason for creating the revised version.] Version#Implemented ByRevision DateApproved ByApproval DateReason1.0 UP Template Version: 11/30/06 Note to the Author [This document is a template of a Change Management Plan document for a project. The template includes instructions to the author, boilerplate text, and fields that should be replaced with the values specific to the project. When using this template for your project document, it is recommended that you follow these steps: TABLE OF CONTENTS 1 Introduction.. 5 1.1 Purpose of The Change Management Plan.. 5 2 Change management Process.. 5 2.1 Change Request Process Flow Requirements. 5 2.2 Change Request Form and Change Management Log. 6 2.3 Evaluating and Authorizing Change Requests. 6 2.3.1 Change Control Board. 7 3 Responsibilities.. 7 Appendix A: Change Management Plan Approval.. 8 Appendix B: References.. 9 Appendix C: Key Terms.. 10 Appendix D: Change Request Form Example.. 11 Appendix E: Change Management Log Template.. 12 1 Introduction 1.1 Purpose of The Change Management Plan [Provide the purpose of the Change Management Plan. This document should be tailored to fit the particular project needs.] The Change Management Plan documents and tacks the necessary information required to effectively manage project change from project inception to delivery. The Change Management Plan is created during the Planning Phase of the project. Its intended audience is the project manager, project team, project sponsor and any senior leaders whose support is needed to carry out the plan. 2 Change management Process The Change Management process establishes an orderly and effective procedure for tracking the submission, coordination, review, evaluation, categorization, and approval for release of all changes to the project’s baselines. 2.1 Change Request Process Flow Requirements [Outline the project team’s agreed upon change request (CR) process flow. The following outlines a generic change request process flow.] StepDescriptionGenerate CRA submitter completes a CR Form and sends the completed form to the Change ManagerLog CR StatusThe Change Manager enters the CR into the CR Log. The CR’s status is updated throughout the CR process as needed.Evaluate CRProject personnel review the CR and provide an estimated level of effort to process, and develop a proposed solution for the suggested changeAuthorizeApproval to move forward with incorporating the suggested change into the project/productImplementIf approved, make the necessary adjustments to carry out the requested change and communicate CR status to the submitter and other stakeholders 2.2 Change Request Form and Change Management Log [List and define the data elements the project team needs to include on the Change Request Form and in the Change Management Log. Examples of these are provided in Appendix D and Appendix E. At a minimum, the following data should be included on the project’s Change Request Form and Change Management Log.] ElementDescriptionDateThe date the CR was createdCR#Assigned by the Change ManagerTitleA brief description of the change requestDescriptionDescription of the desired change, the impact, or benefits of a change should also be describedSubmitterName of the person completing the CR Form and who can answer questions regarding the suggested changePhonePhone number of the submitterE-MailEmail of the submitterProductThe product that the suggested change is forVersionThe product version that the suggested change is forPriorityA code that provides a recommended categorization of the urgency of the requested change (High, Medium, Low) 2.3 Evaluating and Authorizing Change Requests [In order to evaluate and prioritize a change request, the “priority” and “type” of the change are taken into consideration. Use the first and second tables below to list and define the “priority” and “type” data elements that are applicable for the project. The third table provides examples of commonly used project status types. The list of elements is at the discretion of the project manager.] Change requests are evaluated using the following priority criteria: PriorityDescriptionHighMediumLow Change requests are evaluated and assigned one or more of the following change types: TypeDescriptionScopeChange affecting scopeTimeChange affecting timeDurationChange affecting durationCostChange affecting costResourcesChange affecting resourcesDeliverablesChange affecting deliverablesProductChange affecting productProcessesChange affecting processQualityChange affecting quality Change requests are evaluated and assigned one of the following status types: StatusDescriptionOpenEntered/Open but not yet approved or assignedWork in ProgressCR approved, assigned, and work is progressingIn ReviewCR work is completed and in final review prior to testingTestingCR work has been reviewed and is being testedClosedCR work is complete, has passed all tests, and updates have been released. 2.3.1 Change Control Board [A Change Control Board (CCB) is a formally constituted group of stakeholders responsible for approving or rejecting changes to the project baselines. This group may meet on a predefined schedule or on an as needed basis. The table below provides a brief description of personnel acting as the Change Control Board (CCB) and their role/level of authority within that group.] RoleNameContactDescription [Insert Role][Insert Name][Insert Contact #][Insert Role Description] 3 Responsibilities [Provide a brief description of persons responsible for each step of the change management process for the project.] RoleNameContactDescriptionProject Manager Change Manager [Insert Role][Insert Name][Insert Contact #][Insert Role Description] Appendix A: Change Management Plan Approval The undersigned acknowledge they have reviewed the Change Management Plan and agree with the approach it presents. Changes to this Change Management Plan will be coordinated with and approved by the undersigned or their designated representatives. [List the individuals whose signatures are desired. Examples of such individuals are Business Steward, Project Manager or Project Sponsor. Add additional lines for signature as necessary. Although signatures are desired, they are not always required to move forward with the practices outlined within this document.] Signature: Date: Print Name: Title: Role: Signature: Date: Print Name: Title: Role: Signature: Date: Print Name: Title: Role: Appendix B: References [Insert the name, version number, description, and physical location of any documents referenced in this document. Add rows to the table as necessary.] The following table summarizes the documents referenced in this document. Document Name and VersionDescriptionLocation[Provide description of the document] Appendix C: Key Terms [Insert terms and definitions used in this document. Add rows to the table as necessary. Follow the link below to for definitions of project management terms and acronyms used in this and other documents. http://www2.cdc.gov/cdcup/library/other/help.htm The following table provides definitions for terms relevant to this document. TermDefinition[Insert Term][Provide definition of the term used in this document.][Insert Term][Provide definition of the term used in this document.][Insert Term][Provide definition of the term used in this document.] Appendix D: Change Request Form Example The example Change Request From attached below can be used to submit changes during the life of the project. Appendix E: Change Management Log Template The detailed Change Management Log template attached below can be used to track and manage requested changes during the life of the project.
