Tagged: kanban

Lean, Kanban and Large-Scale Agile

Agile methods work beautifully for a single team. But what do you do when you have multiple, interdependent teams, all working on a single product or product suite? How can Agile scale without losing sight of its core principles? In this session, we’ll examine how to apply Lean and Agile...

A Kanban Team and Their Contracts with Partners

One very important property in Kanban is called “make process policies explicit”. This includes well-defined interfaces to upstream as well as downstream partners. Kanban tries to define these interfaces on a very abstract level, because Kanban is a change management approach that wants to integrate with several possible project management...

Scrumban: Combining Scrum and Kanban

Corey Ladas wrote a classic essay on Scrum-ban where he discusses Scrum and Kanban hybrids. He presents the concept of index card and explains that Kanban is more than just a work request on a card and putting sticky notes on a whiteboard is not enough to implement a pull...

State of Kanbanland

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.

A Lean/Kanban Approach to Teams

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, starting...

Kanban Weakspots

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.

An Evolutionary Approach to Implementing XP

In this blog post, Tom Howlett presents how his organization gradually adopted eXtreme Programming (XP) practices. He discussed each XP practices (pair programming, planning game, test driven development, whole team, continuous integration, etc.) and shares his experience for each of them. He also explains their current shift from Scrum to...