Difference between revisions of "Change management (ITSM)"

From wikieduonline
Jump to navigation Jump to search
Tags: Mobile web edit, Mobile edit
Tags: Mobile web edit, Mobile edit
Line 2: Line 2:
  
  
Typical steps on a IT change management
+
Typical steps on a IT change management:
 
* Change planning
 
* Change planning
 
* Change approval
 
* Change approval
 
* Change implementation
 
* Change implementation
 
* Change closure
 
* Change closure
 +
 +
 +
Best practices for a successful change management process:
 +
 +
Change planning
 +
* 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 if there is impact on the service
 +
* Choose the right time according to service to execute you change
 +
 +
Change approval
 +
* Submit your change to [[change-advisory board]] (CAB) for approval
 +
 +
Change implementation
 +
* Verify always your [[backups]] before starting a change which risk your data
 +
* Follow the plan
 +
 +
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.
 +
* Notify stakeholders of change outcome, include any deviation and some verification that the service is working properly
 +
 +
  
 
== See also ==
 
== See also ==
 
* {{ITIL}}
 
* {{ITIL}}

Revision as of 04:51, 16 April 2020

wikipedia:Change management (ITSM)


Typical steps on a IT change management:

  • Change planning
  • Change approval
  • Change implementation
  • Change closure


Best practices for a successful change management process:

Change planning

  • 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 if there is impact on the service
  • Choose the right time according to service to execute you change

Change approval

Change implementation

  • Verify always your backups before starting a change which risk your data
  • Follow the plan

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.
  • Notify stakeholders of change outcome, include any deviation and some verification that the service is working properly


See also

Advertising: