Single-piece flow moves one change through the software workflow at a time: commit a small change, run tests, learn from the result, and adjust before moving on. section 5.4.2
Reliable, immediate feedback supports this flow. When tests are flaky, teams may batch changes to avoid repeated CI delays; failures then become harder to diagnose, and cycle time grows less predictably. section 5.4.2
Flaky CI and larger commits
A developer who delays pushing until several changes accumulate faces a harder question when CI fails: which change caused it? Smaller changes make each failure easier to investigate. section 5.4.2
Figure 5.5 Variability widens cycle time and shifts teams from single-piece flow to batching.

Shows how feedback variability can encourage batching, widen cycle time, and increase diagnostic complexity. section 5.4.2
