How does Kanban differ from Scrum?
Options
- Kanban limits WIP and flows; Scrum uses sprints (Correct option)
- They are identical in the way that they work
- Kanban has fixed sprints, while Scrum does not
- Kanban is only used for hardware engineering
Answer
Kanban uses a visual board, limits work in progress (WIP) and flows continuously without fixed sprints; Scrum works in timeboxed sprints with defined roles and events
Why
Kanban columns show states (To do, In progress, Review, Done). The key rule is WIP limits: a maximum number of items in each column, so you finish work before starting new work, exposing bottlenecks.
No mandatory sprint or roles; changes can be added any time. Metrics: lead time and cycle time.
Support and maintenance teams often prefer Kanban; product teams often use Scrum. Many teams mix them ("Scrumban").
Remember
Kanban = continuous flow + WIP limits. Scrum = timeboxed sprints.