How does Kanban differ from Scrum in Agile?

• A. Kanban includes sprint planning; Scrum does not
• B. Kanban allows for no sprint planning; stories are picked up continuously
• C. Kanban requires detailed documentation for each task
• D. Kanban is less flexible than Scrum

Answer: (B)

Kanban operates on a continuous flow model rather than the time-boxed sprints utilized in Scrum. This means that in Kanban, work items are pulled into the workflow as capacity allows, and there is no specific end date for completing a set of tasks. Teams continuously select and work on tasks based on priority and workload, which allows for a more fluid and adaptive approach to project management.

In contrast to Scrum, which organizes work into distinct sprint cycles with defined goals and deadlines, Kanban promotes an ongoing process where tasks can be added, removed, or reprioritized at any time based on the needs of the team and project. This flexibility enables teams to respond to changing priorities more readily without waiting for a sprint to end, making it an effective approach in environments where workloads fluctuate.

This is why the statement regarding Kanban allowing continuous picking of stories is accurate and distinguishes it from the structured planning inherent to Scrum.