These are the definitions of the DORA Metrics we calculate as part of our Insights feature, as well as an explanation of what each metric can indicate.
Change Lead Time (also referred to as Lead Time for Change) is the average amount of time required for a commit to be deployed.
When your team has effective processes in place that enable developers to deploy code to production with minimal friction, your team will begin to see a decrease in the length of its development feedback cycle. When developers can make changes to production in smaller batches, they can more quickly identify and ﬁx issues.
Deployment Frequency is the number of deployments per unit of time.
As your tooling and conﬁgurations mature, you should be able to deploy more frequently. When effective DevOps processes help prevent human error from entering the deployment process, you can deploy more often without fear of breaking your infrastructure.
Change Failure Rate (also referred to as Deployment Failure Rate) is the percentage of deployments that fail to complete successfully.
With effective processes and reliable infrastructure in place, your team should expect the percentage of deployments that fail or need to be cancelled to decrease over time. This metric would serve as a proxy for the effectiveness of a team’s deployment processes as they shift to smaller, more frequent deployments from larger, more complex deployments.
Failed Deployment Recovery Time (FDRT) is the average amount of time it takes to roll back a change.
Of course, even a process that accounts for everything the designer can think of will fail when a new situation is encountered. When things go wrong, your team needs a way to revert the changes quickly; this metric assesses how your developer experience enables the rollback of failed changes.