Develop > Processes and Best Practices > Change Management Overview > Input and output for Change Management

Input and output for Change Management

Changes can be triggered and resolved in several ways. The following table outlines the input and output for the Change Management process.

Input and output for Change Management process

Input to Change Management

Output from Change

  • Policy and strategies for change and release
  • Request for change
  • Change proposal
  • Plans (change, transition, release, deployment, test, evaluation, and rendition)
  • Current change schedule and projected service outage (PSO)
  • Current assets or configuration items
  • As-planned configuration baseline
  • Test results, test report, and evaluation report
  • Rejected Request for Changes (RFCs)
  • Approved RFCs
  • Change to a service or infrastructure
  • New, changed, or disposed assets or CIs
  • Change schedule
  • Revised PSO
  • Authorized change plans
  • Change decisions and actions
  • Change documents and records
  • Change Management reports

Key performance indicators for Change Management

The Key Performance Indicators (KPIs) in the following table are useful for evaluating a Change.

Key Performance Indicators for Change Management

Title

Description

% of unauthorized changes

Percentage of unauthorized implemented changes in a given period. A change in the infrastructure without a registered change request is considered unauthorized.

% of incidents caused by changes

Percentage of incidents caused by the implementation of a change in a given period.

% of emergency changes

Percentage of the total number of closed emergency changes in a given period.

% of successful changes

Percentage of the total number of closed changes successfully implemented in a given period.

% of backed out changes

Percentage of the total number of closed changes for which a remedy plan is activated in a given period.

% of rejected changes

Percentage of the total number of closed changes rejected in a given period.

Average time per phase

Average amount of time spent on each of the distinct change phases in a given period.

Validation, Risk and Impact Analysis, TCAB Approval, Build and Test, DCAB Approval, Deployment, Post Implementation Review, CMDB Update, and Closure.

For completeness, the ITIL 2011 and COBIT 4.1 KPIs are included in the following sections.

ITIL 2011 Key Performance Indicators

The following are ITIL 2011 KPIs for Change Management:

  • Number of changes implemented to services that met customer requirements (for example, quality/cost/time expressed as a percentage of all changes).
  • Benefits of change expressed as the value of improvements made added to the value of negative impacts prevented or terminated as compared to the costs of the change process.
  • Reduction in the number of disruptions to services, defects, rework caused by inaccurate specification, and poor or incomplete impact assessment.
  • Reduction in the number of unauthorized changes.
  • Reduction in the backlog of change requests.
  • Reduction in the number and percentage of unplanned changes and emergency fixes.
  • Change success rate (percentage of changes deemed successful at review, that is, the number of RFCs approved).
  • Reduction in the number of changes in which remediation is required.
  • Reduction in the number of failed changes.
  • Average time to implement based on urgency/priority/change type.
  • Incidents attributable to changes.
  • Percentage accuracy in change estimate.

COBIT 4.1 Key Performance Indicators

The following are the COBIT 4.1 KPIs for Change Management:

  • Number of disruptions or data errors caused by inaccurate specifications or incomplete impact assessment.
  • Extent of application rework caused by inadequate change specifications.
  • Minimum time and effort required to make changes.
  • Percentage of emergency fixes.
  • Percentage of unsuccessful changes to the infrastructure due to inadequate change specifications.
  • Number of changes not formally tracked, reported, or authorized.
  • Number of backlogged change requests.
  • Percentage of changes recorded and tracked with automated tools.
  • Percentage of changes that follow formal change control processes.
  • Ratio of accepted and refused change requests.
  • Number of different versions of each business application or infrastructure being maintained.
  • Number and type of emergency changes to the infrastructure components.
  • Number and type of patches to the infrastructure components.