Change Management

Unit 06

Change Management
Content:

Change Management objective and overview Some definitions Responsibilities and obligations Important aspects:
RFC content Categorization and prioritization of changes Change Advisory Board (CAB) Interface to other processes Benefits and risks

Best practices Summary

Change Management

Best Practices

Concurrent integration with configuration and release management

Include the development environment in the change management process

separately from the production environment

Assign process responsibility, if possible, independently from the organisations

hierarchy

Conceive separate procedure for urgent changes and standard changes instead of
using the normal change management process

Change Management

Summary

The goal of the change management process is to ensure that standardized

methods and procedures are used for efficient and prompt handling of all changes, in order to minimize the impact of change-related incidents upon service quality, and consequently to improve the day-to-day operations of the organization.

Implement only authorized changes; minimize risk and costs. Request for Change (RFC) applies to all components of the IT infrastructure Tasks
Requests for change management, authorize and plan changes, monitor realization, test and implementation, support the ongoing needs of business

CAB and Emergency Committee Severity/Priority: urgent, high, medium, low Effect - Category: none to significant effect Back-out procedure Process is always closed with change review