Leadership asks for a single DORA metric that answers how often the team delivers value to users, reported as a throughput count over a window rather than as any elapsed duration, so they can compare release cadence against an industry benchmark. Which metric should the team report?
- ALead time, calculated from when a change is requested until it reaches production, which reports the elapsed duration a single change takes to travel through the delivery pipeline.
- BChange failure rate, calculated as the share of deployments that cause a production failure needing remediation, which reports how risky the team's releases are to ship.
- CCycle time, calculated from a developer's first commit until the change reaches production, which reports how long active development and delivery take for a single item.
- DDeployment frequency, calculated as the number of successful production deployments completed in a window, which reports how often the team releases value as a throughput count. Correct
Why A is wrong: Lead time is a DORA flow metric but expresses an elapsed duration per change, not a throughput count of how often the team ships, so it answers the wrong shape of question.
Why B is wrong: Change failure rate is a DORA stability metric about release quality, not a count of how often the team deploys, so it does not express delivery cadence.
Why C is wrong: Cycle time is an elapsed-duration measure for one item's active development, so it cannot serve as the throughput count of releases per window leadership wants.
Why D is correct: Deployment frequency is the DORA flow metric expressed as a count of production deployments per window, which is exactly the cadence throughput figure leadership asked to benchmark.