Module 02 Course Project – Change Management Template and Change Request Form Module 02 Course Project – Change Management Template and Change Request Form
You may use outside sources to complete these documents. If you source something elsewhere, follow the integrity of the language, but make the document your own. Do not copy/paste from other established documentation.
There are examples in the templates, but there are many deviations and styles that can be used.
Change Request Form Version: 1.0
Change Request Form (e xample)
Having Trouble Meeting Your Deadline?
Get your assignment on Module 02 Course Project – Change Management Template and Change Request Form Module 02 Course Project – Change Management Template and Change Request Form completed on time. avoid delay and – ORDER NOW
|
SUBMITTER – GENERAL INFORMATION |
||||
|
CR# |
||||
|
Submitter Name |
||||
|
Brief Description of Request |
||||
|
Date Submitted |
|
|||
|
Date Required |
||||
|
Priority |
|_| Low |
|_| Medium |
|_| High |
|_| Mandatory |
|
Reason for Change |
||||
|
Other Artifacts Impacted |
||||
|
Assumptions and Notes |
||||
|
Attachments or References |
|_| Yes |
|_| No |
||
|
Link: |
|
INITIAL ANALYSIS |
||
|
Hour Impact |
||
|
Duration Impact |
||
|
Schedule Impact |
||
|
Comments |
||
|
Recommendations |
|
CHANGE CONTROL BOARD – DECISION |
||||
|
Decision |
|_| Approved |
|_| Approved w/Conditions |
|_| Rejected |
|_| More Info |
|
Decision Date |
||||
|
Decision Explanation |
||||
|
Conditions |
Revision Date: 1/1/2018 Page 1
Change Request Form
,
<Organization Name>
<Organizational Name>
Change Management PLAN
Version < >
<mm/dd/yyyy>
<Project Name> Change Management Plan Version: <1.0> <Draft>
Revision Date: Error! Unknown document property name. Page 2 of 12
CDC_UP_Change_Management_Plan_Template.doc
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 By |
Revision Date |
Approved By |
Approval Date |
Reason |
|
1.0 |
<Author name> |
<mm/dd/yy> |
<name> |
<mm/dd/yy> |
<reason> |
Note to the Author
[This document is a template of a Change Management Plan. The template includes instructions to the author, boilerplate text, and fields that should be replaced with the values specific to the organization.
· Red italicized text enclosed in square brackets ([text]) provides instructions to the document author, or describes the intent, assumptions and context for content included in this document.
· Red italicized text enclosed in angle brackets (<text>) indicates a field that should be replaced with information specific to the organization.
· Text and tables in black are provided as boilerplate examples of wording and formats that may be used or modified as appropriate to your organization. These are offered only as suggestions to assist in developing your organizational plan.
When using this template for your project document, it is recommended that you follow these steps:
1. Replace all text enclosed in angle brackets (i.e., <Organizational Name>) with the correct field values. These angle brackets appear in both the body of the document and in headers and footers. To customize fields in Microsoft Word (which display a gray background when selected):
1. Modify boilerplate text as appropriate to your organization.
2. To add any new sections to the document, ensure that the appropriate header and body text styles are maintained. Styles used for the Section Headings are Heading 1, Heading 2 and Heading 3. Style used for boilerplate text is Body Text.
3. To update the Table of Contents, right-click and select “Update field” and choose the option- “Update entire table”
4. Before submission of the first draft of this document, delete this “Notes to the Author” page and all instructions to the author, which appear throughout the document as red italicized text enclosed in square brackets.]
TABLE OF CONTENTS
1.1 Purpose of The Change Management Plan 4
2.1 Change Request Process Flow Requirements 4
2.2 Change Request Form and Change Management Log 5
2.3 Evaluating and Authorizing Change Requests 5
Appendix A: Change Management Plan Approval 7
Appendix D: Change Request Form Example 10
Introduction
Purpose of The Change Management Plan
[Provide the purpose of the Change Management Plan. This document should be tailored to fit the particular organizational needs.]
The Change Management Plan documents and tracks the necessary information required to effectively manage change from the 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.
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.
Change Request Process Flow Requirements
[Outline the project teams agreed upon change request (CR) process flow. The following outlines a generic change request process flow.]
|
Step |
Description |
|
Generate CR |
A submitter completes a CR Form and sends the completed form to the Change Manager |
|
Log CR Status |
The Change Manager enters the CR into the CR Log. The CR’s status is updated throughout the CR process as needed. |
|
Evaluate CR |
Project personnel review the CR and provide an estimated level of effort to process, and develop a proposed solution for the suggested change |
|
Authorize |
Approval to move forward with incorporating the suggested change into the project/product |
|
Implement |
If approved, make the necessary adjustments to carry out the requested change and communicate CR status to the submitter and other stakeholders |
Change Request Form and Change Management Log
[List and define the data elements the project team needs to include on the Change Request Form. Examples of this is provided in Appendix D. At a minimum, the following data should be included on the project’s Change Request Form.]
|
Element |
Description |
|
Date |
The date the CR was created |
|
CR# |
Assigned by the Change Manager |
|
Title |
A brief description of the change request |
|
Description |
Description of the desired change, the impact, or benefits of a change should also be described |
|
Submitter |
Name of the person completing the CR Form and who can answer questions regarding the suggested change |
|
Phone |
Phone number of the submitter |
|
|
Email of the submitter |
|
Product |
The product that the suggested change is for |
|
Version |
The product version that the suggested change is for |
|
Priority |
A code that provides a recommended categorization of the urgency of the requested change (High, Medium, Low) |
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:
|
Priority |
Description |
|
High |
<Insert the definition the project assigns to a high priority CR> |
|
Medium |
<Insert the definition the project assigns to a medium priority CR> |
|
Low |
<Insert the definition the project assigns to a low priority CR> |
|
<priority> |
<Insert the definition the project assigns to this level of priority CR> |
Change requests are evaluated and assigned one or more of the following change types:
|
Type |
Description |
|
Scope |
Change affecting scope |
|
Time |
Change affecting time |
|
Duration |
Change affecting duration |
|
Cost |
Change affecting cost |
|
Resources |
Change affecting resources |
|
Deliverables |
Change affecting deliverables |
|
Product |
Change affecting product |
|
Processes |
Change affecting process |
|
Quality |
Change affecting quality |
|
<change type> |
<define this change type> |
Change requests are evaluated and assigned one of the following status types:
|
Status |
Description |
|
Open |
Entered/Open but not yet approved or assigned |
|
Work in Progress |
CR approved, assigned, and work is progressing |
|
In Review |
CR work is completed and in final review prior to testing |
|
Testing |
CR work has been reviewed and is being tested |
|
Closed |
CR work is complete, has passed all tests, and updates have been released. |
|
<status type> |
<define this status type CR> |
Change Control Board
[A Change Control Board (CCB) is a formally constituted group of stakeholders responsible for approving or rejecting changes to within the organization. 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.]
|
Role |
Name |
Contact |
Description |
|
[Insert Role] |
[Insert Name] |
[Insert Contact #] |
[Insert Role Description] |
Responsibilities
[Provide a brief description of persons responsible for each step of the change management process for the project.]
|
Role |
Name |
Contact |
Description |
|
Project 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 <Project Name> 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.]
|
Date: |
|||
|
Print Name: |
|||
|
Title: |
|||
|
Role: |
|
Signature: |
Date: |
||
|
Print Name: |
|||
|
Title: |
|||
|
Role: |
|
Signature: |
Date: |
||
|
Print Name: |
|||
|
Title: |
|||
|
Role: |
[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 Version |
Description |
Location |
|
<Document Name and Version Number> |
[Provide description of the document] |
<URL or Network path where document is located> |
[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.
The following table provides definitions for terms relevant to this document.
|
Term |
Definition |
|
[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 attached example Change Request Form can be used to submit changes during the life of the project.
Page 10 of 10
image1.wmf