liveBook · Manning

Metric

As explained in Build High Value Software Systems

A metric is a quantitative measure of a property or outcome of a process, system, or activity.

A metric turns an otherwise hard-to-see process condition into a number a team can investigate. Useful metrics reveal where work waits or value stalls; a better number is not necessarily evidence of a better system. section 9.0

Use metrics as signals for learning, not rankings of individuals. For example, a cycle-time spike led a team to find that rotating on-call duties delayed code reviews. Creating review windows around those shifts addressed the process cause, and cycle time stabilized. section 9.1.1

A diagnostic metric can become harmful when treated as a target. Cutting integration tests to meet a build-time goal made builds faster but allowed regressions through. Ask whether improving the number also improves the system—and what behavior the target might encourage. section 9.1.2

Figure 9.2 Every metric follows one of two paths. The left path improves the system. The right path games the number.

Compare the path from a metric to system improvement with the path that games the number. section 9.1.2

How Build High Value Software Systems covers it

How deep it goes
Distinguishes learning signals from rankings and targets through software-delivery examples, without detailing measurement calculations.
Examples
Uses cycle-time spikes caused by review delays and build-time targets that remove integration tests.
What you can do after
Evaluate whether a measure supports learning or encourages behavior that worsens delivery.
How it connects
Connects metrics to cycle time, Goodhart's law, and system-level improvement.

Also explained in

Compare how 20 books explain metric →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build High Value Software Systems. The section links point to the parts of the book it draws on.