Continuous increment
Description
Unlike iterative increment, which packages work into fixed time pulses (sprints), continuous increment generates a steady flow of deliveries: each user story moves independently through the workflow and is delivered to production as soon as it is done, without waiting for the end of a cycle.
The principles of continuous increment come from lean manufacturing and the Toyota Production System: produce at the moment it is needed, minimize waiting times, and keep a low WIP so that the flow is predictable.
Advantages
- More frequent value delivery: the customer receives features as soon as they are ready.
- Lower risk of accumulation: problems become visible immediately, without waiting for the end of the sprint.
- Greater flexibility in the face of priority changes: if a high-priority story comes up, it can enter the flow without waiting for the next sprint.
Challenges
Achieving continuous flow without sprints is not easy:
- Bottlenecks tend to form, blocking progress in some stages while others are left without work.
- Without the sense of urgency that the sprint provides, procrastination or delay may set in (→ Parkinson's Law).
- Capacity planning and feedback meetings require their own mechanisms.
The answer to these challenges is the WIP limit and flow management through the kanban board.
Common mistake
Confusing continuous increment with "there is no process." Continuous increment is not the absence of structure: it is a different structure. Without WIP limits, without flow metrics (lead time, cycle time), and without meetings to review the value stream, "continuous flow" degenerates into chaos, with multiple open stories that nobody finishes.
See also
Do you want to advance in agility? You can search for course and exam calls or go at your own pace by becoming a member of the Agile Club. This membership includes exclusive resources, e-learning classrooms, and access to Skill Arena: a space to practice and measure your agile skills at your own pace.