Change Management Best Practices

This KB outlines some basic guidelines for maintaining Change Management best practices.

Scope

  • Files CRs for Production Services
  • Files CRs for significant Non-Production changes
    • Version Releases
    • Non-routine configuration changes
    • Support and Handling Changes
    • Documenting changes to test/dev environments
  • Not filing CRs for inconsequential/insignificant changes

Timing

  • Files CRs in with more than enough lead time (versus just in time filing)
    • Normal CRs are filed at least 48 hours before implementation
    • Limit amount of Emergency CRs filed

Accuracy

  • CRs clearly define scope of work
  • CRs clearly indicate impact to services/CIs
  • CIs are linked approprately to CR
  • Completes CR following implementation
    • Mark ‘Actual Start/End Dates’
    • Set as ‘Complete’

Communication

  • Stakeholders are updated reliably
  • Additional communication (if necessary) is completed
  • Communicates any unknowns or additional risks that are discovered directly to Change Manager

Other references:

[Link for document 42213 is unavailable at this time]
DoIT Operational Framework - Section 3.0 - Change Management



Keywords:change management best practices operational framework change request   Doc ID:116466
Owner:Ramsay B.Group:DoIT IT Service Management
Created:2022-02-03 09:35 CSTUpdated:2022-02-03 09:45 CST
Sites:DoIT IT Service Management, DoIT Staff
Feedback:  0   0