The Agile Software Development movement has been around 11 years, and yet few seem to understand the true issues that challenge us and why Agile methods help. However, adopting Agile approaches has proven challenging for many firms. In this talk, David Anderson, a leader in the Agile movement will outline, the essence of Agile methods, why they are proving hard to adopt at large scale, and an alternative approach to agility using the Kanban Method.
Discover how a team of sysadmins dragged the best of Kanban, added a chunk of Scrum and came up with a clear and sustainable process for support teams.
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.
Many teams who are already using Scrum would like to know what benefits they can get by moving to Kanban. Dropping the Sprint timebox can seem quite scary but on the other hand spending less time planning and estimating seems attractive to many developers. How do you know that you haven’t thrown the baby out with the bathwater?
In this short video, a development manager explains how they use Scrum for development work in the sprints, but use KanBan to deal with issues with released software in the field. Their helpdesk prioritises the issues and the team uses the KanBan board to solve these issues as fast as possible.
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.