Change management overview

Change management is an IT service management process. The objective of change management in this context is to ensure that standardized methods, procedures,documentation and communications are used for efficient and prompt handling of all changes occurring to IT infrastructure and applications, It also minimizes possible number of incidents and impact on related services.

Change management request (CMR)

In IT terminology a request for change is called a Change management request (CMR) or a change request.Users or parties who want any change can request for that change using CMR. A CMR then categorized, scheduled, planned, approved, executed, verified, documented, communicated and closed.

Change management flow

  • Submission
  • Categorized
  • Scheduled
  • Planned
  • Approved/Analyzed
  • Executed
  • Verified
  • Documented
  • Communicated
  • Closure

Change Management is a process used for managing the planned deployment of alterations to all configuration items in the configuration management database (or “CIs” in the CMDB), that are a part of a business’s live (“production”) and test (“UAT”) environments along with any other environment that a business wants to have under Change Management. It is not typically responsible for change within development environments.

A change is an event that is:

  • Approved by management
  • Implemented with a minimized and accepted risk to existing IT infrastructure
  • Results in a new status of one or more configuration items (CIs)
  • Provides increased value to the business (Increased Revenue, Avoided Cost, or Improved Service) from the use of the new or enhanced IT systems.

Change Advisory Board

Any proposed change must be approved in the change management process. While change management makes the process happen, the decision authority is the Change Advisory Board (CAB), which generally is composed of people from other functions within the organization. The main activities of the change management are:

  • Filtering changes
  • Managing changes and the change process
  • Chairing the CAB and the CAB/Emergency committee
  • Reviewing and closing of Requests for Change (RFCs)
  • Management reporting and providing management information

What happens if Change management is not used?

  • No Change Management Means Poor Project Results
  • No configuration database will be there and nowhere to manage information and properties of infrastructure and applications.
  • No communication to teams of changes going on so lot of incidents.
  • No analysis of impact of changes.
  • No fail-over and roll-back plans so there will be lot of chaos if change fails.
One Comment

Add a Comment

Your email address will not be published. Required fields are marked *