The short version
| Scrum | Kanban | |
|---|---|---|
| Rhythm | Fixed sprints, usually 1–4 weeks | Continuous flow |
| Roles | Product Owner, Scrum Master, Developers | No required roles |
| Limiting work | Sprint commitment limits what is taken on | Explicit WIP limits per stage or person |
| Change mid-cycle | Discouraged during a sprint | Allowed any time a slot frees up |
| Key metrics | Velocity, burndown | Cycle time, throughput, WIP |
| Meetings | Planning, daily scrum, review, retrospective | None required; many teams hold a short daily standup and periodic reviews |
How Scrum works
Scrum divides time into sprints. At sprint planning the team chooses a set of items from the product backlog that it believes it can finish. During the sprint it meets daily, and at the end it shows the work in a sprint review and reflects in a retrospective. The Product Owner owns priorities; the Scrum Master helps the team follow and improve the process.
Scrum’s strength is rhythm. Every few weeks there is a natural moment to plan, show work and improve. Its weakness is rigidity when work is unpredictable: a production bug does not wait for the next sprint.
How kanban works
Kanban has no sprints. Work flows across the board continuously, and the main control is the WIP limit: when a column is full, you finish something before starting something new. Priorities can change at any moment, because the next card is only chosen when there is room for it. See what is kanban for the basics.
Kanban’s strength is responsiveness and low overhead. Its weakness is that without a rhythm, teams can forget to step back, plan and improve.
Which one should you choose?
Choose Scrum when you build a product in increments, can protect the team from interruptions for a couple of weeks at a time, and benefit from regular demos to stakeholders.
Choose kanban when work arrives unpredictably (support, operations, bug fixing, content, personal work), when the team is small, or when you want to improve your current process gradually rather than adopt a new one.
Use both (Scrumban) when you like sprint planning and retrospectives but want WIP limits and the freedom to pull urgent work in. This is what most small software teams end up doing in practice.
Scrumban in practice
- Plan every two weeks, but pull cards one at a time instead of committing to a fixed list.
- Keep WIP limits on In progress and Review.
- Hold a short retrospective at the end of each cycle.
- Measure cycle time instead of story points.
The sprint board template is set up for exactly this.
Common myths
- “Kanban means no planning.” Kanban teams plan constantly; they just plan smaller and more often.
- “Scrum boards are kanban boards.” They look alike, but a board without WIP limits is a task board, not a kanban system.
- “You must pick one.” Methods are tools. Use what helps.