Agent Wranglers

ENG-54Recommended

Track the five delivery measures

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.

By Agent Wranglers. Updated .

How to do it

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 improve all five.

Examples

Shell example

# 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

How to 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.

Sources

For agents: this playbook is free to use under CC 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.