9.2

9.2 Metric definitions and formulas reference

Every formula from the book, gathered in one place. Each entry names the topic with the full discussion, including its gaming risk and guardrail. Use this as a quick lookup, not a substitute for the topic itself.

Flow metrics (Part 2)

MetricFormulaTopic
Flow velocityCount of flow items completed per unit time2.3
Flow distribution(Completed items of one flow item type) / (Total completed items) x 100%2.3
Flow timeTime from a flow item entering the value stream to its delivery2.4
Flow loadCount of flow items currently active or waiting in the value stream2.4
Little’s lawFlow load (work in process) = Arrival rate x Flow time (cycle time)2.4, 2.7
Flow efficiencyActive work time / Total elapsed time x 100%2.5
Cycle timeSum of stage durations: coding + pickup + review + test + deploy2.6
UtilizationArrival rate / Service rate2.7
Percent complete and accurate (%C/A)(Units usable downstream without rework) / (Total units) x 100%2.8
Rolled throughput yield%C/A of stage 1 x %C/A of stage 2 x … x %C/A of stage N2.8
Takt timeAvailable working time / Customer demand over that period2.8
Time to first reviewTime from pull request opened to first substantive reviewer response2.9
Deployment frequencyCount of successful production deployments per unit time2.10
Lead time for changesTime from first commit to successful production deployment (report median and 90th percentile)2.10
Change failure rate(Deployments causing a failure) / (Total deployments) x 100%2.10
Failed deployment recovery timeTime from failure detection to genuine service restoration2.10

Developer experience (Part 3)

MetricFormulaTopic
Focus timeCount and duration of uninterrupted two-hour-plus blocks per week, from calendar data3.6
Response rate(Survey responses received) / (Survey invitations sent) x 100%3.7

Code and quality (Part 4)

MetricFormulaTopic
Cyclomatic complexityIndependent paths through control flow (edges − nodes + 2, per McCabe)4.1
Test coverage(Lines/branches executed by tests) / (Total lines/branches) x 100%4.2
Mutation kill rate(Mutants killed by test suite) / (Total mutants introduced) x 100%4.2
Code churnLines added + modified + deleted per file over a time window4.3
Hotspot scoreChurn x Complexity, ranked per file4.3
Debt carrying costEstimated ongoing cost of not fixing an item (slower related work, elevated defect risk)4.5

Product and business (Part 5)

MetricFormulaTopic
Escaped defect rate(Severity-weighted escaped defects) / (Unit of delivery or time)5.1
Initial adoption(Users who tried the feature at least once) / (Target audience) x 100%5.2
Retained adoption(Users still using the feature after N weeks) / (Users who initially tried it) x 100%5.2
Unit costTotal cost (people + infrastructure + tooling) / Meaningful unit (customer, transaction)5.4
ROI(Total benefit − Total cost of ownership) / Total cost of ownership, presented as a range5.5

Reliability, operations, and security (Part 6)

MetricFormulaTopic
Error budget(1 − SLO target) x Time window (e.g., 0.1% of 30 days ≈ 43 minutes)6.1
Error budget burn rateError budget consumed / Error budget allotted, over a given window6.1
MTTDTime from incident onset to detection6.2
MTTATime from incident notification to acknowledgement6.2
MTTR (incident)Time from acknowledgement to genuine service restoration6.2
On-call page distributionPages received per individual, over a rolling window (not team average)6.3
Vulnerability time-to-remediateTime from discovery to genuine remediation, tracked by severity6.4

Notes on using these formulas

  • Always pair a speed or output formula with its guardrail (topic 1.2): change failure rate with deployment frequency and lead time; escaped defect rate with delivery speed; error budget burn with deployment activity.
  • Use medians and percentiles, not averages, for time-based formulas (topic 1.6) unless a formula explicitly calls for a mean.
  • Every formula needs a documented source system and collection method (topic 1.5) alongside its mathematical definition; two teams computing the same formula from different sources will not produce comparable numbers.
  • Severity weighting is not shown explicitly in every formula above but applies wherever “severity-weighted” appears; see the relevant topic for the full classification scheme.