Home › The Garage › Scrum & Kanban
Transformation

Scrum & Kanban for delivery

Both are agile; they organise the work differently. Scrum packages work into fixed sprints with set roles. Kanban keeps a continuous flow and limits work in progress. The right choice depends on how your work actually arrives.

By LeanBean · Updated November 2026 · 5 min read
What's in this guide
  1. How Scrum works
  2. How Kanban works
  3. The real differences
  4. Which to choose
  5. Common questions
Scrum 2-weeksprint plan → build → review → repeat Kanban To do DoingWIP 2 Done
Scrum works in fixed sprints; Kanban flows continuously with a cap on work in progress.

How Scrum works

Scrum organises delivery into fixed-length sprints (often two weeks). The team commits to a set of work at the start, builds it, and reviews a working increment at the end, then repeats. It has defined roles — a product owner who owns priorities, a scrum master who clears obstacles, and the delivery team — and a rhythm of ceremonies: planning, a short daily sync, review and retrospective. The cadence creates predictability.

How Kanban works

Kanban has no sprints and no prescribed roles. Work flows across a board continuously, pulled through as capacity frees up, with a work-in-progress limit that caps how much is in play at once. Priorities can change at any time — you simply pick the top of the queue next. It optimises for smooth, responsive flow rather than a fixed commitment per cycle.

The real differences

Which to choose

Match the method to how work arrives
Scrum suits work you can plan into batches and a team that benefits from a steady rhythm — feature development, project delivery. Kanban suits work that arrives unpredictably and must be responsive — support, operations, a shifting backlog. Many teams run a blend. Choose by the shape of your demand, not by which word sounds more agile.

Describe a process. Get the whole analysis.

LeanBean turns a plain-language description of any process into a professional map — with Lean waste, SIPOC, design-thinking, AI-readiness and capacity analysis built in, and a Transformation Coach that sequences the fixes. Free to start.

Build your first map free →

The Garage — a community of practice

The Garage is where Lean, process and AI-readiness practitioners learn in the open — short lessons, real examples, and a place to compare notes. Join the community: follow along, try it on your own work, and share what you find.

Common questions

What is the difference between Scrum and Kanban?

Scrum organises work into fixed-length sprints with defined roles and ceremonies and a per-sprint commitment. Kanban has no sprints or prescribed roles — work flows continuously, pulled through under a work-in-progress limit, and priorities can change at any time.

What are the roles in Scrum?

A product owner who owns priorities and the backlog, a scrum master who removes obstacles and protects the process, and the delivery team who build the increment. Kanban, by contrast, prescribes no roles.

Does Kanban have sprints?

No. Kanban uses continuous flow rather than fixed iterations. Instead of committing to a batch per sprint, the team limits work in progress and pulls the next item when capacity frees up.

How do I choose between Scrum and Kanban?

Match the method to how work arrives. Scrum suits plannable, batchable work that benefits from a steady rhythm; Kanban suits unpredictable, responsive work such as support or operations. Blending the two is common and legitimate.

Related guides: Agile vs waterfall · Kanban & pull systems · Ways of working