Change management
Change in the IT environment is ubiquitous - it can occur reactively or proactively. Both require a good change management process to manage the lifecycle of all changes and to ensure standard procedures for assessing and implementing them. This minimizes the risk of introducing new potential problems.
Default process template
This is a default process template that can be further modified by the customer according to their needs.
| Status | Description | Instructions for solvers |
|---|---|---|
| New | A change ticket is being classified. | Check that this is a "Change request". If not, use the "Move to another service" command to move the ticket to the correct service. Determine the priority of the solution. Then use the "Assign" command to assign the ticket to a specific solver for analysis. |
| Analysis | Analysis and design changes are in progress. | Study the proposal for change. Check with the sponsor that you have a good understanding of the requirement. Develop the change proposal. |
| Approval | Approval of the proposed amendment is pending. | Use the "Allow approval" command to forward the proposed change for approval. After successful approval, forward it for scheduling. |
| Planning | Planning is underway to implement the change. | Plan to implement the change. When the time is right, pass the ticket to implementation. |
| Implementation | The change is being implemented. | Implement the change according to the approved design. |
| Testing | Testing is ongoing after the change is made. | Test the change against the approved design. |
| Closed | The ticket has been closed. The ticket is closed. |