Change Stages - Overview
|
|
|
|
Submission |
Deciding Change Template and Change Workflow, Configuring Change Related Details like Change Type, Risk Involved, Priority, Urgency etc., |
Requested Requested for Info Submitted for Authorization Accepted/Rejected
|
Requested>>Submitted for Authorization >>[Requested for Info]>>Accepted/Rejected
Authority Directly Involved: Change Requester and Line Manager |
Planning |
Analyzing and Working Out Change Impact, Roll Out Plan, Backout Plan, Checklist and Downtime concerned with the Change |
Planning In Progress Requested for Info Approved/Rejected Submit for Review
|
Planning In Progress>> Submit for Review>> [Requested for Information] >>Approved/Rejected
Authority Directly Involved: Change Planning Team, Change Owner |
Approval |
Convening CAB(s) (Change Advisory Board) to assess change plans and get their approval for change implementation. |
Approval Pending
Approved/Rejected |
Approval Pending>>Approved (or) Rejected
Authority Directly Involved: Change Advisory Board (CAB), Change Manager
|
Implementation |
Implementing Change through Projects and Tasks, Estimating Change Implementation team’s activities using Worklogs and informing them about Downtime Scheduling (as per the Change Plans) |
In Progress Requested for Information Onhold/Backout Completed
|
In Progress>>[Requested for Info] >[OnHold]>>Completed [Back Out]
Authority Directly Involved: Change Implementation Team,Change Owner |
|
Review |
Reviewing Change-to-be-Implemented and deciding whether it can be implemented or not |
In Progress
Completed (or)
Failed
|
In Progress>>Completed/Failed
Authority Directly Involved: Change Review Team |
Close |
Formal closing of Change by associating it with a suitable closure code that represents how the change was closed. |
In Progress Completed Cancelled
|
In Progress >>Completed/Cancelled Closure Code Selection (depending on how the change was closed)
Authority Directly Involved: Change Manger, Change Requester |
|
|
Note:
|
