Scrum, Kanban, Scrumban: there are many approaches to manage product development and project in the Agile software development world. It is a good thing to have multiple Agile tools, but you should also know when to use them. In this article Brendan Marsh of Spotify explains why his team dropped Scrum for Kanban just before launching their product.
In this blog post, Cory Foy explains how he recreated Scrum using Kanban coupled with a set of Explicit Policies. Kanban has less initial rules than Scrum, but the team decides with explicit policies how he wants to manage things like the frequency of the meetings with the backlog owner. The blog post describes the right set of explicit policies needed in Kanban to recreate Scrum. As Cory Foy says, this is a little bit a silly exercise, but it allows also to think about the implicit set of policies that Scrum proposes.
In this blog post, Ken Pugh compares the usage of Kanban board and Scrum tracking boards to track progress of agile projects. He concludes that Scrum-style boards and Kanban-style boards can provide the same information, but in different ways.
In this blog post, Samuli Heljo shares his experience about a Scrum team that transitioned to Kanban. It offers a lot of data about this experience and try to analyze the failures made and to come up with some solutions.
Thinking about Lean as a combination of science, management and learning provides Scrum practitioners to start with including Lean and Kanban practices into their Scrum practices. Explicit policies, managing work-in-progress, and creating visibility have a direct, measurable impact on a team’s velocity.
“Aspects of Kanban” is an introduction to the Kanban workflow Lean project management system.
Scrum Expert Copyright © 2009-2026 Martinig & Associates