Cadence Decoupling

Definition

Timeboxed Agile methods bundle prioritization, development, and delivery into a single fixed-length iteration — everything is planned, built, and shipped on the same cycle. Kanban dispenses with the timebox and instead decouples these activities, letting each find its own cadence: delivery might happen every two weeks, prioritization might happen weekly or on demand, and individual work items flow through development at whatever rate their size and complexity dictate. A regular cadence is preserved — Kanban still delivers "on the Principles Behind the Agile Manifesto" — but the different coordination activities are no longer forced to march in lockstep.

In the Book

Chapter 8 traces a specific failure mode in fixed-iteration Agile: as teams learned that smaller batches flow better, they shortened iterations (Scrum from four weeks to two, Extreme Programming from two weeks to one), which made it harder to write user stories small enough to fit — leading teams either to revert to longer iterations or to split a story across three iterations of analysis, coding, and testing, which "disguise[s] the fact that work is actually still in progress when it is being reported as completed." Kanban instead separates the lead time for developing a story from the delivery cadence and from the prioritization cadence, on the reasoning that "coordination effort around delivery is surely different from the coordination effort around prioritization of new work." Chapter 8 details the coordination and transaction costs of setting a delivery cadence — using the 2002 Sprint PCS network upgrade, which required training 17,000 retail staff, as an example of how expensive a release event can be to coordinate. Chapter 9 does the same analysis for the prioritization cadence, treating it as a separate scheduling decision with its own costs.

Why It Matters

Bundling unrelated coordination activities into one cycle length forces a compromise: whatever cadence best suits planning also has to suit shipping, even though the two involve different people, different costs, and different natural rhythms. Decoupling cadences is a general move for any system with multiple coordination rhythms competing for a single shared cycle — it lets each activity be scheduled at the frequency its own transaction costs actually justify, rather than at whichever frequency the loudest or most visible activity requires.