IT Operating Environments Best Practices

Overview

The environment pipeline is the operational mechanism through which the organization’s delivery capability functions. Its performance - how frequently deployments occur, how long they take from commit to delivery, how often they introduce failures, and how quickly failures are recovered from - directly determines the organization’s ability to deliver value to its users at the speed and quality that competitive and operational requirements demand. These are the four key metrics of software delivery performance that research in the field of DevOps and continuous delivery has consistently identified as the most predictive indicators of organizational delivery capability: deployment frequency, lead time for changes, change failure rate, and mean time to recover. Measuring them provides the organization with an objective, comparable picture of its delivery pipeline performance and a basis for targeted improvement investment.

Best Practice

Instrument the deployment pipeline to measure all four key delivery performance metrics across every environment tier, with visibility into both the aggregate pipeline performance and the performance at individual environment gates. Deployment frequency measures how often deployments to each environment tier occur - higher frequency indicates a more active, more iterative delivery discipline. Lead time for changes measures the time from a code commit to deployment to each environment tier - shorter lead time indicates a more efficient pipeline with less wait time between stages. Change failure rate measures the percentage of deployments to each environment tier that result in an environment incident or a rollback - lower failure rate indicates higher deployment quality and more effective gate validation. Mean time to recover measures the average time required to restore normal environment operation following a deployment-related failure - shorter recovery time indicates more effective incident response and rollback capability. Report these metrics at the pipeline level and by environment tier, and use them as primary inputs to delivery process improvement and environment governance investment decisions.

Benefit(s)

Measuring deployment pipeline performance with the four key delivery metrics provides the organization with an objective, quantitative picture of its delivery capability that subjective quality assessments cannot provide. Bottlenecks in the pipeline are visible as lead time concentrations at specific gates. Delivery quality is measurable as change failure rates by environment tier. Recovery capability is quantifiable as mean time to recover by environment. The organization can set specific, measurable improvement targets for each metric and track progress against those targets, directing investment to the specific pipeline stages and environment tiers where performance improvement will produce the greatest delivery capability benefit.