Demand-Capacity Balance¶
Definition¶
Demand-capacity balance is the explicit management of the ratio between work arriving into a system and the capacity available to complete it. Rather than accepting all incoming work and letting teams absorb the overload, this practice makes both demand and capacity visible and manageable. Scrumban enables this through WIP limits, classes of service that sort work by risk and delivery cadence, and metrics that reveal where demand exceeds capacity. Importantly, balancing includes "demand shaping"—consciously deciding which work to accept, which to defer, and which to reject—rather than attempting to expand capacity to match unlimited demand.
In the Book¶
Reddy argues that the Kanban Method "directly addresses the challenge of balancing demand against capability" more than any other framework, including Scrum. The book emphasizes that this goes beyond simply limiting work in progress; it includes awareness of non-value-adding demands and active reduction of waste. A concrete example: software teams often respond to requests for information about future work that may never occur, or reserve capacity to handle unpredictable, disruptive demands. Scrumban visualizes these patterns and enables teams to make deliberate trade-offs: Do we reserve 20% capacity for unplanned work, or do we require ad hoc requests to queue? Does this particular customer request actually align with our service-level expectations?
The book connects this to the Kanban Method's sustainability agenda: sustainable pace is not achieved by working harder but by limiting how much work is in flight at any moment, which also improves system agility by maintaining slack—the available options to respond to change.
Why It Matters¶
This concept prevents the silent dysfunction where teams say "yes" to everything and then either miss commitments or burn out achieving them. By making demand and capacity explicit and visible, teams gain leverage to have honest conversations about priorities and trade-offs. It also enables forecasting: once you know your sustainable capacity and how much demand arrives, you can predict when promises can be safely made. Organizationally, it shifts the conversation from "work harder" to "manage demand," from a moral failure model to a systems design model.