Pragmatic Cadence Choice

Definition

Scrumban rejects the notion that time-boxed iterations (sprints) are always preferable or that continuous flow is always optimal. Instead, it enables teams to make an informed choice based on their specific circumstances: team maturity, skill stability, resource sharing constraints, and business cadence. Time-boxed iterations create synchronized commitment points and coordination rhythms that can be valuable; continuous flow enables predictability and eliminates sprint starvation for some contexts. The key principle is that this choice should be made consciously, with understanding of what each mode optimizes for and what it trades away.

In the Book

Reddy critiques Corey Ladas's original Scrumban formulation—which advocated moving away from sprints toward continuous flow—as context-specific rather than universally optimal. The book argues that "factors favoring time-boxed practices include the depth of skills and maturity of your teams, the stability of the members in those teams, and the extent to which key resources must be shared." The contrasting case studies illustrate this: Objective Solutions, with mature teams coordinating across 15–50 teams with a monthly release cadence, found continuous flow ideal for eliminating sprint starvation and managing complexity. Mammoth Bank's less-experienced teams continued using time-boxed sprints because "regular interactions around the work were beneficial in helping members improve their shared understanding of both the work and the sprint goals." The book emphasizes that this pragmatic choice—either path represents an acceptable outcome—is precisely what distinguishes Scrumban from purist approaches.

Why It Matters

This concept allows organizations to move beyond theological debates about frameworks and focus instead on outcomes. It recognizes that some constraints are artifacts of context, not eternal truths: a startup with a small, co-located team of generalists may thrive with continuous flow, while a large, distributed enterprise with specialists must synchronize via sprints. It also enables evolution: a team can start with sprints (useful structure for new learners) and migrate toward continuous flow as maturity and context change. Most importantly, it frames this choice as part of systems design rather than as failure to "do Scrum right."