Software Success Metrics


Measuring the effectiveness of software change

Delivering software at speed by focusing on change failure rates and mean time to recover.

Defining Success

Industry data shows that high performing software organizations are able to outperform their peers in each of three key outcomes, each measured by two metrics.

Efficiency: Effectiveness of software change. Efficiency is measured by:

  • Change failure rate
  • Mean time to recover

Speed: The rate of software change.
Learn more about measuring and managing speed.

Risk: Quality of software change.
Learn more about measuring and managing risk.

You can start by focusing on any of these outcomes individually, but long-term success requires addressing each of them.

Defining Performance

Improving the service availability and resilience in your organization starts with assessing your current state. Industry data categorizes IT organizations into the following high, medium, and low performing categories based on speed. Where does your organization fall?

High Performers Medium Performers Low Performers
Change Failure Rate
Change Failure Rate


Mean Time to RecoverMean Time to Recover
< 1 Hour
<1 Day
<1 Day

Notice the "operational chasm" as organizations transition from low-performing to high-performing, where failure rates increase. This is caused by stumbles as an organization learns to use new tools, processes and automation. We have guided organizations through this chasm and can help you avoid common pitfalls. 

Increasing Service Resiliency

Automate deployments management to lower change failure rate and decrease the time to recover from service failures.

  1. Build
    Provision new environments quickly, test changes and dependencies automatically.
  2. Deploy:
    Automatically test, review, build, and deploy changes on commit.
  3. Manage:
    Automatically correct compliance issues and configuration drift.

Start with our webinar