Scrum vs Kanban: Sprints or Continuous Flow, and How to Choose
By the end of this lesson you'll be able to:
- Explain how scrum and kanban differ in rhythm, roles and planning
- Say what a sprint and a WIP limit are, and why each matters
- Choose scrum, kanban or a mix for a real team
Quick answer: scrum vs kanban, what is the difference?
Scrum organizes work into fixed-length sprints of one month or less, with a product owner, a scrum master and developers. Kanban organizes work as a continuous flow on a board, with limits on work in progress and no required roles. This Kanbanchi lesson shows when each one fits and how to choose.
Sprints vs continuous flow in 9 slides
One idea per slide. Use the buttons, the dots or your arrow keys. The full text of every slide is right below the player.
Lesson 5 slides
9 slides
The full lesson: scrum and kanban, side by side
Scrum vs kanban in one sentence
Scrum organizes work into fixed-length sprints; kanban organizes it as a continuous flow with limits on work in progress. Both are agile ways of working, and both use a board. The difference is the rhythm. Agile is an iterative approach: the team delivers working pieces in short cycles, gets feedback after each one and adjusts the plan as it goes. Its values come from the 2001 Agile Manifesto. You met both in Lesson 3: Project management methodologies; this lesson puts them side by side.
What is scrum?
Scrum is an agile framework in which a small team works in fixed-length sprints of one month or less, often two weeks, with three accountabilities: product owner, scrum master and developers. The product owner decides what is most valuable to build next and orders the product backlog. The scrum master helps the team use scrum well and removes obstacles. The developers are the people who do the work, whatever their job titles.
The scrum cycle: plan the sprint, work with a daily scrum, review the increment, improve the process, repeat.
Sprints and the scrum events
A sprint is a fixed-length period of one month or less, often two weeks, in which a scrum team turns the items it selected from the product backlog into a usable increment. Each sprint has sprint planning, a short daily scrum, a sprint review of the increment and a retrospective. Planning picks the work and sets a sprint goal. The daily scrum is a 15-minute check on progress toward that goal. The review shows stakeholders what was built and gathers feedback, and the retrospective asks how the team can work better in the next sprint.
What is kanban?
Kanban is a flow method: the team shows all work on a board, limits how much work is in progress at once and pulls new work only when there is capacity, without fixed-length iterations. Kanban does not ask you to change roles or job titles: you start with the process you have, make it visible and improve it step by step. Cards move from left to right, for example from To do to In progress, Review and Done.
WIP limits: the heart of kanban
A work-in-progress (WIP) limit is the maximum number of cards allowed in one column of a kanban board at the same time. When a column is full, the team finishes something before starting anything new. That is what keeps work flowing. Without limits, a board turns into a long list of half-finished cards; with them, bottlenecks show up as a full column that everyone can see. When one card gets stuck, some teams have several people work on it together until it moves again; Kanbanchi's guide to swarming explains when that helps.
Kanban teams measure flow, mainly cycle time: how long one card takes from start to done. Shorter, more predictable cycle times mean the team can promise dates with more confidence.
The key differences between scrum and kanban
Scrum: a fixed rhythm, three accountabilities, change waits for the next sprint. Kanban: continuous flow, no required roles, new work can be pulled as soon as there is capacity. The table compares them point by point.
| Scrum | Kanban | |
|---|---|---|
| Rhythm | Fixed-length sprints of one month or less, often two weeks | Continuous flow, no fixed iterations |
| Roles | Product owner, scrum master and developers | No required roles; keep your current ones |
| Planning | Sprint planning at the start of every sprint | Pull the next card when there is capacity |
| Limiting work | The sprint backlog limits work for the sprint | WIP limits on each column of the board |
| Change | New work usually waits for the next sprint, so the sprint goal stays fixed | New work can be added to the backlog at any time and pulled next |
| Key measure | How much the team completes per sprint | Cycle time: how long one card takes from start to done |
| Board | Reset at the start of each sprint | Persistent: cards keep flowing across it |
| Best for | Product work that benefits from regular reviews of a working increment | Steady streams of requests, support and operations work |
When to choose scrum
Choose scrum when you build a product in pieces and want a working increment and stakeholder feedback at a regular rhythm. It suits a stable team that can protect a sprint from interruptions. If urgent requests land every day, those interruptions break the sprint, and scrum starts to feel like overhead.
When to choose kanban
Choose kanban when requests arrive all the time and priorities change daily, such as support, marketing requests or operations. It is also the easiest start: you can put your current work on a board today. The risk is drift: without sprint reviews, a kanban team has to schedule its own reviews of the work and the process.
Scrumban: combining scrum and kanban
Many teams keep sprints and reviews from scrum and add WIP limits from kanban to the sprint board. This mix is often called scrumban. Pick the rhythm first, then borrow the practices you need. A typical scrumban team plans in short cycles, limits the cards in each column, and pulls the next card as soon as there is room instead of waiting for the next planning meeting. It suits teams that like a regular review but get too many interruptions to protect a full sprint. If you are still deciding between a plan-first and an adapt-as-you-go approach overall, start with Lesson 4: Agile vs waterfall.
Exercise: sort the practices, then choose for real teams
Two quick steps with instant feedback on every answer.
Step 1: scrum, kanban or both?
0 of 8 right
Sort each practice. You get feedback on every answer, and you can try again until it is right.
Worked example
"Work is split into small cards on a board" is Both: scrum and kanban teams both break work into small items on a board. Now sort the 8 practices below.
1. Work is planned in two-week sprints.
Answer: Scrum. Fixed-length sprints of one month or less are the core of scrum.
2. Each column has a maximum number of cards.
Answer: Kanban. WIP limits on columns are the core practice of kanban.
3. The team uses a board to make work visible.
Answer: Both. Both methods use a board. Scrum resets its board each sprint; a kanban board keeps flowing.
4. A scrum master helps the team and removes obstacles.
Answer: Scrum. The scrum master is one of the three scrum accountabilities, with the product owner and the developers.
5. A new urgent card can be pulled as soon as someone has capacity.
Answer: Kanban. Kanban has no iterations, so new work can be pulled whenever a WIP limit allows it.
6. The team holds a retrospective to improve how it works.
Answer: Scrum. The retrospective is a defined scrum event at the end of every sprint. Kanban teams often hold reviews too, but kanban does not require a fixed retrospective.
7. The team measures cycle time from start to done.
Answer: Kanban. Cycle time is the main flow measure in kanban.
8. The team delivers in small pieces and adjusts based on feedback.
Answer: Both. Both are agile ways of working, built on small pieces of work and feedback.
Step 2: which fits this team better?
0 of 4 right
Pick the better starting point for each team, based on how their work arrives.
Worked example
A legal team reviewing contracts that arrive at random, each needing a quick answer, fits Kanban: the work arrives continuously, so a sprint would keep being interrupted. Now choose for the 4 teams below.
1. An IT help desk with new tickets arriving all day.
Answer: Kanban. Requests arrive continuously and priorities change daily, which is the case for kanban.
2. A product team building a new mobile app feature by feature, with a monthly demo for stakeholders.
Answer: Scrum. Building a product in increments with regular reviews is what scrum is designed for.
3. A marketing team handling requests from five departments, each with its own deadline.
Answer: Kanban. A steady stream of mixed requests suits continuous flow with WIP limits.
4. A new team starting a six-month software project that needs regular feedback from users.
Answer: Scrum. Regular sprint reviews give the users a working increment to react to at a fixed rhythm.
Knowledge check: Lesson 5
Five questions on this lesson. Get at least 4 right to complete Lesson 5 and move your course progress forward. Each answer comes with an explanation.
Key takeaways
- Scrum works in fixed-length sprints of one month or less, with a product owner, a scrum master and developers.
- Kanban is a continuous flow with WIP limits on each column and no required roles.
- Choose by how work arrives: a product built in increments suits scrum; a steady stream of requests suits kanban.
- Scrumban combines them: keep the sprints and reviews of scrum and add the WIP limits of kanban.
Try it on a real board: scrum or kanban in Kanbanchi
Kanbanchi, the task and project management app that works inside Google Workspace, supports both ways of working. Try one in a few minutes:
- Create a board with four lists: To do, In progress, Review and Done.
- For kanban: set a card limit of 2 on In progress and Review, and pull the next card only when a list has room.
- For scrum: add a Sprint backlog list, move in the cards for the next two weeks and give them due dates on the last day of the sprint.
- Hold a short review at the end of the sprint, then move unfinished cards back to the backlog.
- Use the Gantt chart view if you need to show stakeholders the dates.
This step is optional. The course works without an account, and your progress does not depend on it.
Scrum vs kanban: FAQ
What is the main difference between scrum and kanban?
Rhythm. Scrum works in fixed-length sprints of one month or less with three defined accountabilities. Kanban works as a continuous flow, with limits on how many cards can be in progress at once and no required roles.
Is kanban agile?
Yes. Kanban is a flow method used by many agile teams: work is delivered in small pieces, the board makes it visible, and the team improves the process step by step.
Can you use scrum and kanban together?
Yes. Many teams keep sprints and reviews from scrum and add WIP limits from kanban, a mix often called scrumban. Choose the rhythm first, then borrow the practices you need.
Which is better for beginners, scrum or kanban?
Kanban is usually easier to start: you put your current work on a board, set a WIP limit and improve from there. Scrum asks for new roles and events, but gives a stronger rhythm once the team is used to it.