The scheme below illustrates state models of the change requests of three different types:
Also, you can find a brief description of every state further in the article.
Normal Change model is relevant when the Change Authority field has the Local Authorization value. In this case, the Authorization stage is skipped. |
This state is for the newly created change requests.
This state is mandatory for Normal or Emergency changes. In this state, the request must be reviewed and authorized by the responsible persons or groups (see more on the Change Request Authorization). After all authorization steps have been passed, the change request transitions to the Scheduled state.
In this state, the change request has the following prerequisites:
So it is preliminary known when the change will be implemented.
This state displays that the request is in progress of implementation now. When the work is over, the state has to be changed to Completed.
When the Assigned User field changes its value, the change state changes from the In Progress to Assigned value. |
After the work is over and the request is transited into this state, the requester can perform the tests and give feedback on the results of the implementing. After this, change the state to Closed.
When the request is completed (whether successfully or not), the Change Advisory Board (CAB) has a right to perform Post Implementation Review on the basis of the implementing. It is a good practice that allows gaining the "lessons learned" after the implementation, especially if there were any issues on the way.
For this, the change request state must be changed to the Post Implementation Review state from the Completed state. After the review, similarly to the Completed state, mark it as Closed.
All activities on this change request are over, and it cannot be reopened.