Change Management Process
Change Management exists to coordinate and inform customers and staff of all changes that impact any shared computing system or service. The overriding goal is to provide a high level of availability and service to our customers.
Change Management is the process of communicating, coordinating, scheduling, and monitoring change.
Change Management has the responsibility to insure that appropriate documentation, testing, and notification, training (customers and staff), and backout procedures are in place for each change requested.
The purpose of Change Management is not to question the rationale of a change, but to insure that all elements are in place, all parties notified and trained, and the schedule for implementation is coordinated with all other activities in the organization.
Goals
Ensure that standardized methods, processes and procedures are used for all changes
Effective and fast handling of all changes
Maintain the balance between the need of a change and the possible damage related to changes
Scope
Configuration Items (CI) for QA and Production. (2010)
Hardware
Software
Documentation
Procedures related to Operations, support and maintenance
Keywords
Request for Change (RFC)
Change Priority - Risk Assessment, Initial Impact, Urgency, Priority
Change Model - Major/Significant/Minor Roll out/ Minor
Technical/Express/Standard/Emergency/Correction
Change Advisory Board (CAB)
Change Advisory Board/Emergency Committee (CAB/EC)
Forward Schedule of changes (FSC)
Post Implementation Review (PIR)
Process Overview