DORA Metric
A DORA Measure is a DevOps performance measure produced by DORA.
- Context:
- …
- Example(s):
- Lead-Time for Changes (between code commit and releasable code).
- Deploy Frequency.
- Mean Time to Restore (MTTR) (time to restore service when a service incident).
- Change Fail Rate (CFR).
- …
- Counter-Example(s):
- See: [[]].
References
2022
- https://devops-research.com/quickcheck.html
- QUOTE: ... Measure your team's software delivery performance in less than a minute! Compare it to the rest of the industry by responding to five multiple-choice questions. Compare your team's performance to others, and discover which DevOps capabilities you should focus on to improve. We don't store your answers or personal information. ...
2017
- (Forsgren et al., 2017) ⇒ Nicole Forsgren, Monica Chiarini Tremblay, Debra VanderMeer, and Jez Humble. (2017). “DORA Platform: DevOps Assessment and Benchmarking.” In: International Conference on Design Science Research in Information System and Technology, Springer. doi:10.1007/978-3-319-59144-5_27
- QUOTE: ... IT performance is comprised of four measurements: lead time for changes, deploy frequency, mean time to restore (MTTR), and change fail rate. Lead time is how long it takes an organization to go from code commit to code successfully running in production or in a releasable state. Deploy frequency is how often code is deployed. MTTR is long it generally takes to restore service when a service incident occurs (e.g., unplanned outage, service impairment). Change fail percentage are the percentage of changes that result in degraded service or subsequently require remediation (e.g., lead to service impairment, service outage, require a hotfix, fix forward, patch).
Key capabilities are measured among four main dimensions. The technical dimension includes practices that are important components of the continuous delivery paradigm, such as: the use of version control, test automation, deployment automation, trunk-based development, and shifting left on security. The process dimension includes several ideas from lean manufacturing such as: visualization of work (such as dashboards), decomposition of work (allowing for single piece flow), and work in process limits. The measurement dimension includes the use of metrics to make business decisions and the use of monitoring tools. And finally, the cultural dimension includes measures of culture that are indicative of high trust and information flow, the value of learning, and job satisfaction. ...
- QUOTE: ... IT performance is comprised of four measurements: lead time for changes, deploy frequency, mean time to restore (MTTR), and change fail rate. Lead time is how long it takes an organization to go from code commit to code successfully running in production or in a releasable state. Deploy frequency is how often code is deployed. MTTR is long it generally takes to restore service when a service incident occurs (e.g., unplanned outage, service impairment). Change fail percentage are the percentage of changes that result in degraded service or subsequently require remediation (e.g., lead to service impairment, service outage, require a hotfix, fix forward, patch).