You’ll often hear the question: “Which is better? Kanban or Scrum?” or variations of this eternal deathmatch between two of the most well-established agile methodologies.
People are wasting energy fighting over which methodology trumps another. If you’re an agile organization, you should be placing principle above practice.
It makes a lot of sense to ask questions like “why might I want to use Kanban over Scrum?”, or even “Kanban and Scrum” as opposed to “Kanban vs Scrum”. There are a lot of differences between the two, but fundamentally, they are both agile methodologies, and the principle behind why you might want to use both can be in alignment.
You may even find they can work well together, as part of a unified strategy referred to as Scrumban. You need to consider what approach will work best for your team.
My aim with this article is to approach the question of “Kanban vs Scrum” by clearly presenting both approaches in terms of when, how, and why you might choose to use either of them.
I’ll also talk about the capacity for overlapping Kanban and Scrum approaches, and how some additional tools like Process Street can factor into that equation.
Here’s a breakdown of how we’ll approach comparing “Kanban vs Scrum”:
- What makes a team agile?
- What is Kanban?
- What is Scrum?
- Kanban vs Scrum: Differences
- Kanban vs Scrum: Similarities
- What is Kanban good for?
- When to use Kanban
- Kanban process
- What is Scrum good for?
- When to use Scrum
- Scrum process
- Using BPM for agility
Let’s start with a basic primer on what it means to be agile. Continue Reading