25 Configuration Management and Change Management Metrics You Can't Miss

By: Sasha Gilenson

In today's complex and highly dynamic environment, succeeding in keeping your IT environment and business services running effectively with as little disruptions as possible is not an easy task. So if we do not measure where we are going then we are sure to get somewhere, but probably not where we would like to be. With so many possible metrics to follow, what are the top ones you should follow to succeed in your configuration management, change management, incident management, release management, problem management, availability management key process?

If we do not measure where we are going then we are sure to get somewhere, but probably not where we would like to be.

Below are the key metrics we've identified from the book Metrics for IT Service Management, that you can apply to guide your IT organization to success.

Incident Management
* Percentage of incidents resolve by 1st line support
* Average time to resolve
* First time Right Resolution
* Percentage of proactively solved incidents
See how you can cut incident investigation time and restore a normal service operation as quickly as possible, see the Evolven Configuration Management solution (http://www.evolven.com/).

Configuration Management
* Number of unauthorized configurations
* Number of incidents from failed changes
* Number of breached SLA because of CMDB errors
Learn how to redefine your Configuration Management approach and identify unauthorized configurations at the most granular level (http://www.evolven.com/).

Change Management
* Percentage of failed changes
* Number of unauthorized changes
* Outages during changes
* Percentage of changes on time
* Percentage of changes causing incidents

Release Management
* Number of incidents caused by releases
* Percentage of releases on time

Problem Management
* Total number of incidents
* Total user downtime
* Cost for resolving a problem

Availability Management
* Downtime, unavailability of services
* Incident resolution time
* MTBSI (mean time between system incidents)
* First fix rate

Risk Management
* Percentage of impact to schedule
* Amount of cost difference
* Amount of resources used

Article Directory: http://www.articletrunk.com

| More

A Configuration Management Expert - Sasha Gilenson, CEO at Evolven ( www.evolven.com/ ). Sasha writes about configuration management, change management, cloud configuration, release management, vitualization, incident management.

Please Rate this Article


Not yet Rated

Click the XML Icon Above to Receive Software Articles Articles Via RSS!

Powered by Article Dashboard