liveBook · Manning

Baseline

As explained in Build High Value Software Systems

An initial measurement of a process or system that provides a reference for comparison with later measurements.

A baseline is a measurement of a process before a change, giving the team a reference for judging whether an improvement helped. Measure the friction point directly rather than relying on memory or impressions. section 15.8 section 10.1.4

For a useful comparison, choose a metric that matches the problem and record how it was measured. After making one specific change, measure the same thing the same way again, then compare. If the result improves without harming something else, standardize the change; otherwise, revert it or try another approach. section 10.1.4 section 15.8

PR review time

A team records a baseline median review time of 2.8 days across 14 pull requests. It adds automatic reviewer assignment and a four-business-hour review SLA, then measures again next sprint. The median falls to 1.1 days, supporting the decision to standardize the change. section 10.3.1

How Build High Value Software Systems covers it

How deep it goes
Explains metric selection and same-method before-and-after comparison, then uses results to standardize or revert a change.
Examples
Measures PR review time, CI flakiness, manual deployment steps, and release duration as process baselines.
What you can do after
Practice a measure-change-measure cycle and use the comparison to standardize or revert a process change.
How it connects
Connects baselines to Kaizen, retrospectives, Gemba walks, lead time, cycle time, and control charts.

Also explained in

Compare how 27 books explain baseline →

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.