Agile vs Scrum vs Kanban: What the Difference Is
Agile is a set of values, Scrum is a framework with roles and ceremonies, and Kanban is a flow method. Learn how they relate.
By Velloreth
The three terms
Agile is a set of values and principles. The Agile Manifesto states four preferences: individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan.
Scrum is a framework that applies those values. It defines roles, ceremonies and a fixed-length iteration.
Kanban is a flow method. It defines a board, work-in-progress limits and a continuous pull of work.
The relationship: Agile is the goal, and Scrum and Kanban are two ways to pursue it. A team can be Agile with either, and a team can follow Scrum’s ceremonies without being Agile.
Scrum
Roles: a product owner, a scrum master, and the development team.
Ceremonies:
| Ceremony | Purpose |
|---|---|
| Sprint planning | choose the scope for the sprint |
| Daily standup | surface blockers |
| Sprint review | show the increment to stakeholders |
| Retrospective | improve the process |
The sprint is a fixed-length iteration, usually two weeks. The scope is committed at planning and does not change during the sprint.
The artifacts are the product backlog, the sprint backlog, and the increment.
The strength is the regular cadence and the explicit commitment. A team that struggles to finish work benefits from the boundary.
The weakness is the ceremony. A team with an unpredictable workload, such as a support team, finds a fixed sprint scope artificial.
Kanban
The board has columns that represent the stages of the work, such as To Do, In Progress and Done.
The work-in-progress limit caps how many items can be in a column at once.
| To Do | In Progress (2) | Review (1) | Done |
|-------|-----------------|------------|------|
| ... | ... | ... | ... |
The limit is the mechanism. It forces the team to finish work before starting more, which reduces the time an item spends in progress. A team that is always starting and never finishing is a team without a limit.
The flow metrics are the ones worth tracking:
- Lead time — from request to delivery
- Cycle time — from start to delivery
- Throughput — items delivered per period
- WIP — items in progress
Little’s Law relates them: the average cycle time equals the average WIP divided by the throughput. Reducing WIP reduces the cycle time, which is why the limit works.
The strength is the fit with an unpredictable workload. A new request is added to the board and pulled when capacity allows.
The weakness is the lack of a planning boundary. A team that needs a regular commitment may find the continuous flow harder to plan around.
The comparison
| Concern | Scrum | Kanban |
|---|---|---|
| Cadence | fixed sprints | continuous |
| Commitment | per sprint | per item |
| Roles | defined | none required |
| Ceremonies | four | optional |
| Change | at the boundary | any time |
| Metric | velocity | cycle time |
| Best for | a product backlog | a support or flow workload |
Choosing
A product team with a roadmap: Scrum, because the sprint gives a planning boundary and the review gives a feedback point.
A support or operations team: Kanban, because the work arrives unpredictably and a fixed sprint scope is artificial.
A team new to both: start with Kanban. It needs less ceremony, and the board makes the work visible immediately, which is the first problem to solve.
A team that has Scrum but no flow discipline: add work-in-progress limits to the sprint board. This is Scrumban, and it is a small change with a large effect.
The part that matters
The method is not the goal. A team that follows every Scrum ceremony and ships nothing has not become Agile. A team with a simple board and a weekly review that ships and learns has.
The feedback loop is the goal. The shorter the loop from an idea to a user’s reaction, the faster the team learns. Scrum shortens it with a sprint, and Kanban shortens it with a small batch.
The measurement is the check. A process that is not measured cannot be improved. Velocity, cycle time and throughput are the numbers that show whether a change helped.
Common mistakes
Treating Agile as a process to install. It is a set of values, and a tool does not make a team Agile.
A standup that is a status report. The purpose is to surface a blocker, not to report to a manager.
A retrospective with no change. A meeting that produces no action is a meeting that will be resented.
A work-in-progress limit that is ignored. A limit that is exceeded whenever it is inconvenient is not a limit.
A sprint scope that changes daily. The commitment is the point. A scope that changes is a Kanban board with extra meetings.
Measuring velocity across teams. Velocity is a planning aid for one team, not a productivity comparison.
A quotable summary
Agile is a set of values, Scrum is a framework with roles, ceremonies and fixed sprints, and Kanban is a flow method with a board and work-in-progress limits. Scrum commits to a scope per sprint and changes it at the boundary; Kanban flows continuously and changes whenever capacity allows. The method matters less than the feedback loop it creates, and the measurement is what shows whether a change helped.
Related reading
For the planning side, see estimating-software-tasks and for the review, git-code-review. For the broader context, writing-design-docs and technical-debt-conversation.