Kanban guide · Kanban compared
Kanban vs Agile: How Kanban Fits Into Agile
Kanban and Agile aren't competitors. Agile is a set of values and principles; Kanban is one method that applies them, with roots in Lean manufacturing rather than software.
Key takeaways
- Agile is a mindset; Kanban is a method that applies it.
- Kanban comes from Lean and focuses on flow.
- Kanban evolves your existing process rather than replacing it.
The short answer
Agile is the mindset described in the Agile Manifesto. Kanban is a method for managing flow that is widely used to practise Agile. Kanban fits Agile's emphasis on delivering value continuously, responding to change and improving regularly.
Where Kanban aligns with Agile
- Continuous delivery of value.
- Welcoming changing priorities: new work can be pulled at any time.
- Sustainable pace through WIP limits.
- Regular reflection through cadences and reviews.
- Transparency through visual boards.
Where Kanban is different
| Typical Agile frameworks (e.g. Scrum) | Kanban | |
|---|---|---|
| Origin | Software development | Lean manufacturing |
| Time structure | Fixed iterations | Continuous flow |
| Change approach | Adopt a new framework | Evolve your current process |
| Focus | Delivering increments | Optimising flow |
Using both
Kanban can be used on its own as an Agile method or combined with other frameworks, for example Scrum teams using Kanban boards and WIP limits. See Kanban vs Scrum.
Frequently asked questions
Kanban vs Agile: is Kanban an Agile methodology?
Yes, Kanban is generally classed as an Agile method, although it comes from Lean manufacturing rather than the original Agile software movement.
Can a team practise Agile and Kanban without Scrum?
Yes. Many teams practise Agile principles using Kanban alone.
What is the difference between Kanban and Agile?
Agile is a set of values and principles for delivering work iteratively and responding to change. Kanban is a specific method, focused on visualising work and limiting WIP, that many teams use to work in an Agile way.
How do Kanban and Agile fit together?
Kanban is widely treated as one of the Agile approaches, alongside Scrum and XP, even though its roots are in Lean manufacturing. See types of Agile methodologies.
Are Kanban and Agile both rooted in Lean?
Kanban is: it comes from Lean thinking at Toyota, while Agile grew out of the software movement behind the 2001 Agile Manifesto. Kanban shares Agile's focus on customer value, feedback and continuous improvement, so it is usually counted as both Lean and Agile. See Lean Kanban.
Do Kanban and Agile share the values of the Agile Manifesto?
Kanban was not written from the Agile Manifesto, but it fits its values well, favouring collaboration, working results and responding to change over rigid plans.
Agile vs Kanban: what are the other main Agile frameworks?
Common ones include Scrum, Extreme Programming (XP), Scrumban and scaled frameworks such as SAFe. See Kanban vs Scrum.
Are Kanban and Agile iterative?
Most Agile approaches are iterative and incremental. Kanban is incremental and continuous rather than iterative in fixed cycles: items are delivered one at a time as they are finished, and regular cadences provide feedback.
Can non-software teams use Kanban and Agile?
Yes. Marketing, HR, finance and operations teams often use Kanban as their entry point to Agile because it does not require new roles or Sprints.
Kanban vs Agile: is Kanban a methodology or a framework?
It is usually called a method: the Kanban Method. It provides principles and practices applied to an existing process rather than a fixed set of roles and events.
Agile vs Kanban: which is better?
They are not alternatives. Agile is the philosophy and Kanban is one way to put it into practice, so the real choice is between Kanban, Scrum or another approach.