A team using a hybrid approach must choose between iteration-based agile and flow-based agile for a support workstream where work items arrive unpredictably and vary greatly in size. The team wants to pull the next item as capacity frees up rather than committing to a fixed batch each cycle. Which approach best fits, and what limits work in progress?

Question

Accepted Answer

Flow-based agile, using WIP limits to control the amount of concurrent work. Flow-based (Kanban-style) agile pulls the next item continuously as capacity becomes available, which suits unpredictable, variable-sized work better than fixed-batch iterations. Work in progress is controlled directly by explicit WIP limits, not by sprint commitments, velocity, or estimates.

More Agile Frameworks / Methodologies challenges