jargon

Architecture & practice·Delivery, flow and technical debt

the release contained forty changes, something broke, and the first hour went on working out which one.

Batch size

Also calledsmall batches, change size

How much change moves through the pipeline at once. Almost every delivery improvement is a batch-size reduction in disguise, because small batches are easier to review, faster to test, cheaper to revert and clearer to attribute when they fail. The pressure is always toward larger batches, since each release carries fixed overhead, which is why the sustainable fix is to reduce that overhead rather than to exhort people to ship smaller.

Commonly confused with