DORA metrics are software delivery performance measures covering deployment frequency, lead time for changes, change failure rate, and time to restore service.
DORA metrics assess software delivery performance by showing how quickly changes move to production and how reliably the system operates. section 12.4.3section 16.4.1
The measures cover four complementary aspects of delivery performance:
Deployment frequency measures how often changes are deployed. section 16.4.1
Lead time for changes measures how quickly changes progress toward deployment. section 12.4.3
Change failure rate indicates how often changes fail after release. section 12.4.3
Time to restore service measures how quickly service reliability returns after failure. section 12.4.3
How Architecture Modernization: Socio-technical alignment of software, strategy, and structure covers it
How deep it goes
Defines four delivery measures and positions them as indicators for assessing change speed and system reliability.
Examples
Uses deployment frequency, lead time for changes, change failure rate, and time to restore service as its measures.
What you can do after
Evaluate modernization progress through delivery speed, deployment frequency, change reliability, and service recovery.
How it connects
Connects modernization with deployment frequency, system stability, quality attributes, and broader business metrics.
Platform Engineering on KubernetesA DORA metric is a software delivery performance measure from the DORA research program, including delivery speed, throughput, and stability dimensions.
Effective Platform EngineeringThe DORA framework is a software delivery performance framework centered on deployment frequency, lead time for changes, change failure rate, and time to restore service.
"Looks Good to Me"A software delivery performance measure covering deployment frequency, change lead time, time to restore service, or change failure rate.
change failure ratehas part · Change failure rate is the proportion of deployed software changes that cause failures requiring remediation, rollback, recovery, or other corrective action.
deployment frequencyhas part · Deployment frequency is the rate at which software changes are deployed to a target environment, such as production.
lead timehas part · Lead time is the elapsed time from the initiation, request, or availability of work until its completion or delivery.
mean time to resolutionhas part · Mean time to resolution is the average elapsed time from identifying or reporting an issue, failure, or incident until it is resolved or affected service is restored.
This explainer was generated by Manning's knowledge graph from the text of Architecture Modernization: Socio-technical alignment of software, strategy, and structure. The section links point to the parts of the book it draws on.
