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.
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.
Mike Cottmeyer mixes concepts like Features, User Stories, Story Maps, Minimally Marketable Features, Scrum, Kanban and RUP to create a scalable agile enterprise portfolio framework.
“Aspects of Kanban” is an introduction to the Kanban workflow Lean project management system.