CAPM Practice: Determine how project methodologies influence business analysis processes

Kanban uses continuous flow rather than iterations. BAs keep a 'ready' queue of well-defined items at the top of the backlog, refining items just ahead of when the team will pull them into work — balancing demand and capacity without sprint-based planning cycles.

**Why not A:** Kanban projects do require requirements work, even though they do not use sprint-based planning. Requirements must still be defined, refined, and managed; the difference is that this work flows continuously rather than being organized into sprint-sized batches.

**Why not B:** Batching requirements into large releases planned months in advance contradicts Kanban's continuous flow philosophy. Kanban emphasizes limiting work in progress and delivering value incrementally, not accumulating large batches of work for infrequent releases.

**Why not C:** Requirements in Kanban projects are not solely defined by the development team. BAs, product owners, and stakeholders continue to play essential roles in defining and refining requirements. The continuous flow model changes the timing and cadence of requirements work, not who is responsible for it.