Change Management Fields definition document.

[BoHyun Jung]

If there is a document that defines the meaning and purpose of the fields in the Planning Tab in the Change form,

please give it to me.🤣

• Justification
• Implementation plan
• Risk and impact analysis
• Backout plan
• Test Plan

[Maik Skoddow]

Hi @BoHyun Jung 

I found the following very detailed document for you: https://uit.stanford.edu/sites/default/files/2017/11/22/Change%20Management%20Fulfiller%20guide%20-%... . On page 18 you will find some more information.

And in some different sources I found the following explanations:

Justification

Detailed information explaining why change is being requested and reason it is needed.

Implementation Plan

A change implementation plan is a document that outlines the steps and actions required to execute the approved changes. It includes information such as the scope, objectives, deliverables, schedule, budget, quality, resources, roles and responsibilities, communication, training, and risk management of the change. A change implementation plan helps to ensure that the changes are implemented smoothly and effectively, and that the expected outcomes are achieved. You should update the change implementation plan whenever there are changes in the scope, schedule, cost, quality, or resources of the change.

Test Plan

All Change Requests require that testing be addressed. Change Management is responsible for confirming that a test plan, where feasible, exists. As a rule, testing should be conducted whenever possible; it may include functional, QA, and user acceptance testing, or other testing as appropriate. Additionally, testing should be conducted as possible after a change has taken place as part of a typical implementation plan to ensure that impacted services are fully functional. Ideally, the following information should be included in the Change Request ticket:

• Staff member(s) responsible for testing
• Dates during which testing occurred
• Details of testing environment, as appropriate
• Outcome of testing, with details as appropriat

Back-out Plan

All Change Requests require that back-out measures be addressed. A plan summary should be included in the Change Request ticket. Back-out plans should seek to minimize organizational impact of a failed Change. When possible, it is beneficial to predefine a “trigger” condition that initiates the back-out plan, or identify a specific point in the implementation timeline at which a back-out decision is made. In circumstances in which no back- out plan is feasible, every effort should be made to mitigate the potential risk of organizational impact if the change is unsuccessful. The primary accountability for defining and, if necessary, engaging a back-out plan resides with the requester or implementer of an individual Change Request, or of the project with which the Change Request is associated.

Risk and impact analysis

A change impact analysis is a process that evaluates the effects of a proposed change on the project objectives, deliverables, schedule, cost, quality, resources, risks, and stakeholders. It involves identifying and quantifying the benefits and drawbacks of the change, as well as the dependencies and assumptions involved. A change impact analysis helps to determine the feasibility and viability of the change, and to support the decision making process. You should update the change impact analysis whenever a new change request is submitted or approved.

Maik

[BoHyun Jung · Accepted solution]

Thanks, Maik Skoddow😁

I found descriptions in field dictionary

[Justification]
Enter benefits of implementing this change and impact if this change is not implemented

[Implementation Plan]
Enter sequential steps to implement this change. In addition, enter dependencies between steps and assignee details for each step

[Risk and Impact Analysis]
Enter potential risks and impact associated with this change. Include impact details if this change implementation is unsuccessful

[Backout Plan]
Enter steps to revert the change to its state prior to implementation. Include information regarding when the change can be backed out during implementation and if the change window includes time to backout

[Test Plan]
Enter details of planned and completed tests prior to implementation that indicate the potential success of this change. Enter details of planned post-implementation tests to confirm success of this change