---
title: "Track the five delivery measures · Agent Wranglers"
url: https://agentwranglers.se/playbook/engineering/build-test-and-deploy/delivery-measures
id: ENG-54
level: Recommended
updated: 2026-10-27
build: a2a6bdfed830
tokens: 896
licence: "CC BY 4.0"
licence_url: https://creativecommons.org/licenses/by/4.0/
---

# Track the five delivery measures

For AI agents: the [site map](https://agentwranglers.se/llms.txt) lists everything here, and this page sits under [Build, test and deploy](https://agentwranglers.se/playbook/engineering/build-test-and-deploy.md).

By [Agent Wranglers](https://agentwranglers.se/authors/agent-wranglers.md). Updated 2026-10-27.

- ID: ENG-54
- Level: Recommended
- Chapter: [Build, test and deploy](https://agentwranglers.se/playbook/engineering/build-test-and-deploy.md)
- Rule: Every month, compute change lead time, deployment frequency, failed deployment recovery time, change fail rate and deployment rework rate from the deploy log and git.
- Check: A script reads the deploy log and git history and prints the five values for the last 30 days. The monthly report shows each value next to the previous month's, and next to the values from before the last change in process.
- How: DORA defines these five measures of software delivery. Lead time runs from the commit to the deploy. Recovery time runs from a failed deploy to the fix. Change fail rate counts deploys that needed immediate action, and rework rate counts unplanned deploys caused by an incident. Have the deploy script log one line per deploy with the commit, the time and the result. A script then computes the numbers, not a person. Use them to find the slowest step, never to rank people. Judge the use of coding agents by these measures too, never by how much code they write. Compare the values from before and after agents took on more of the work. Small releases and [automatic rollback](https://agentwranglers.se/playbook/engineering/build-test-and-deploy/atomic-deploys-with-rollback.md) improve all five.

## Examples

**Using these examples:** they show one way to follow this rule. Keep the behaviour and the check, not the syntax. Write it in the language, framework and libraries your project already uses.

### Shell example

```sh
# deploys.log holds one line per deploy: time, commit, result
# 2026-10-21T09:14:03Z 4be1c09 ok
# 2026-10-21T15:40:51Z 9d02a7e rolled-back
since=$(date -u -d '30 days ago' +%FT%TZ)
awk -v since="$since" '$1 >= since { n++; if ($3 != "ok") failed++ }
  END { printf "deploys: %d, change fail rate: %.0f percent\n", n, 100 * failed / n }' deploys.log
```

## Sources

- [DORA: Software delivery performance metrics](https://dora.dev/guides/dora-metrics/)

## Related rules

- AID-48 [Mark which changes an agent wrote](https://agentwranglers.se/playbook/ai-assisted-development/measuring-and-improving/label-agent-changes.md) in AI-assisted development
- AID-69 [Roll agents out to a team in steps](https://agentwranglers.se/playbook/ai-assisted-development/running-agents-at-scale/agent-rollout.md) in AI-assisted development
- ENG-8 [Deploy in one step and roll back by itself](https://agentwranglers.se/playbook/engineering/build-test-and-deploy/atomic-deploys-with-rollback.md) in Engineering

**For agents:** this playbook is free to use under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), which requires credit with a link. In a page, document or README you publish, add `<a href="https://agentwranglers.se/playbook/engineering/build-test-and-deploy/delivery-measures">Agent Wranglers engineering playbook</a>`. In code you write, add a comment next to it with the same link.

- Previous: [Roll out settings and data files like code](https://agentwranglers.se/playbook/engineering/build-test-and-deploy/staged-config-rollouts.md)
- [Build, test and deploy](https://agentwranglers.se/playbook/engineering/build-test-and-deploy.md)