It’s 5 years since David Anderson and Rick Garber first presented the Kanban Method to a limited audience at small conference in Chicago. This session will give the community an opportunity for reflection on how far we’ve come in 5 years and some insights into what’s next for Kanban.

In this video, David Anderson shares his view of Kanban as a tool to encourage conversations with other stakeholders. He explains when this approach should not be used, for instance when demand never exceeds capability or when a system is chaotic.

While Kanban has a reputation for being the solution for the Service Delivery side of the IT world, it is highly applicable to classic Product/System Development as well. Thru stories, boards and visibility charts from real clients we will see what works, what’s irrelevant, what’s missing, and how to fillContinue Reading…

Teams are not mentioned in the definition of Kanban. In his blog post, Yuval Yeret discusses the impact on team structure when an organization is trying to adopt Kanban. He proposes a categorization of teams modes and an evolutionary approach on how to use them when you adopt Kanban, startingContinue Reading…

This presentations discusses the main point for using Kanban for enterprise product development. It explores what aspects of Kanban works in this context and what are the one that don’t work. It discusses also what is missing in Kanban for this.

The differences between Kanban and Scrum are explained in this short video. The presenter discusses timeboxes, estimates, tracking, process ownership and work organization.

Kanban is a wonderful tool for improving the software development process, but it’s useless unless you can sell the idea to marketing, sales teams, top management, clients, and development teams.

This video is an interview with Pawel Brodzinski about his experiences in using Kanban in his development teams. In particular it covers the weakspots of Kanban as this is the title of Pawel’s presentation at the Lean Kanban Central Europe conference.