Difference between revisions of "Change management (ITSM)"
Jump to navigation
Jump to search
Tags: Mobile web edit, Mobile edit |
|||
| (8 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | [[wikipedia:Change management (ITSM)]] | + | * [[wikipedia:Change management (ITSM)]] |
| + | * [[wikipedia:Change management]] | ||
| Line 14: | Line 15: | ||
* Write down all steps of you change, including date, description and executor and roll back procedure in case of failure | * Write down all steps of you change, including date, description and executor and roll back procedure in case of failure | ||
* Review your plan with all stakeholders | * Review your plan with all stakeholders | ||
| − | * Notify and obtain customer approval on advance | + | * Notify and obtain customer approval on advance |
| + | * Assess impact on the service/business ([[Change Impact Analysis (CIA)]]) | ||
* Choose the right time according to service to execute you change | * Choose the right time according to service to execute you change | ||
| Line 21: | Line 23: | ||
=== Change implementation === | === Change implementation === | ||
| − | * Verify always your [[backups]] before starting a | + | * Verify always your [[backups]] before starting and take a new backup before starting |
| − | * Follow the plan | + | * Verify your services are up and running and there is no alerts in the monitoring systems |
| + | * Follow the plan | ||
=== Change closure === | === Change closure === | ||
* Verify always in your [[monitoring]] tool all your services are up and running. If a specific functionality of your stack is not properly monitored prepare some test to verify service. | * Verify always in your [[monitoring]] tool all your services are up and running. If a specific functionality of your stack is not properly monitored prepare some test to verify service. | ||
* Notify stakeholders of change outcome, include any deviation and some verification that the service is working properly | * Notify stakeholders of change outcome, include any deviation and some verification that the service is working properly | ||
| + | |||
| + | |||
| + | == Related terms == | ||
| + | * [[Change Impact Analysis (CIA)]] | ||
| + | * [[ITIL Change Manager]] | ||
== See also == | == See also == | ||
Latest revision as of 08:29, 7 February 2022
Contents
Typical steps on a IT change management[edit]
- Change planning
- Change approval
- Change implementation
- Change closure
Best practices for a successful change management process[edit]
Change planning[edit]
- Write down all steps of you change, including date, description and executor and roll back procedure in case of failure
- Review your plan with all stakeholders
- Notify and obtain customer approval on advance
- Assess impact on the service/business (Change Impact Analysis (CIA))
- Choose the right time according to service to execute you change
Change approval[edit]
- Submit your change to change-advisory board (CAB) for approval
Change implementation[edit]
- Verify always your backups before starting and take a new backup before starting
- Verify your services are up and running and there is no alerts in the monitoring systems
- Follow the plan
Change closure[edit]
- Verify always in your monitoring tool all your services are up and running. If a specific functionality of your stack is not properly monitored prepare some test to verify service.
- Notify stakeholders of change outcome, include any deviation and some verification that the service is working properly
Related terms[edit]
See also[edit]
Advertising:
