In the context of software development, Kanban is an approach based on Lean that tries to limit waste and work in progress to the actual capacity of the software development team. The aim of Kanban is to create a context that balances capacity and demand through a value stream and promote visual project management.
Like the notion of technical debt, the concept of management debt relates to the leadership issues that prevent a successful Agile transformation. This article from Agile transformation expert Sriram Rajagopalan discusses the types of waste that can be eliminated using a Kanban approach and the role of management debt in perpetuating wasteful practices.
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.
Learn how to achieve multiple team collaboration in large scale software development projects. Self-organization is a key concept for all Lean-Agile methods. However, as projects expand across the enterprise and, more specifically, cut across multiple teams, teams clearly can’t just organize in any way they want to. A blend of top-down direction with bottom-up self organization is needed. Lean provides the insights necessary for teams to self-organize within the context of the value stream within which the teams work. A top-down perspective, created by driving from business value, can provide insights on how teams must organize and work together.
Gunther Verheyen presents the the majors aspects of the distinct views of Lean and Agile, indicating the similarities. He elaborates on his statement that the houses of Lean and Scrum are similar houses, just built with different materials. His conclusion is that the open framework of Scrum aligns and blends the underlying thinking of Agile and Lean.
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.