Flow-based agility (e.g., Kanban) and timeboxed agility (e.g., Scrum) represent two distinct approaches to managing work. The primary difference lies in how work is planned and released into the system.
Timeboxed approaches plan work in batches within fixed iterations (typically 1–4 weeks).
Flow-based approaches regulate work continuously based on capacity and demand.
Flow-based Agility (Continuous Flow/Kanban)
- Focus: Continuous, steady flow of work with minimal interruptions.
- Planning: No separate planning event. Planning happens continuously, just-in-time, triggered by capacity availability (not time).
- Work Item Size: Small enough to enable actionable flow signals (WIP liimits, Item Age).
- Best For: Mature teams, maintenance, high-interrupt environments, or teams with varying work types.
- Key Metrics: Cycle time, work-in-progress (WIP), Item Age-In-Progress.
- Advantages: Higher efficiency, faster feedback, better flexibility when priorities change.
Timeboxed Agility (Sprints/Scrum)
- Focus: Fixed-length iterations to deliver a specific set of functionality.
- Planning: Iterative planning at the start of each sprint.
- Work Item Size: Broken down to fit within the Sprint (usually 1-4 weeks).
- Best For: New teams, projects with clear, fixed scopes, or when structure is needed to improve focus.
- Key Metrics: Velocity, sprint burndown.
- Advantages: Predictability, cadence, forced discipline, regular, built-in review/retrospective meetings.
Key Distinction: Flow-based systems do not have an equivalent to Sprint Planning as a discrete, timeboxed event. But they do involve continuous decision-making about what to start next. There is no separate planning event; planning is continuous and demand-driven.