Issue driven kanban standup


Our daily standup is in need of refactoring…recent standup meetings are kind of boring. Each team member does his or her daily blah blah. Time for a change. To tackle this problem, one of the “try this” ideas resulting from our retrospective was to have an issue driven standup. Recently we switched to a more kanban-like process with focus on issues. Therefore the amount of WIP is limited, so going through the work should be doable within the 15m time box we usually need for the standup.

We tried this:

The last question Q3: “when will the issue move to the next lane?”,  is important for the member working in the next column. i.e. a system tester. The tester will know what to expect in his column and he can anticipate on this.

The team reacted enthusiastically to the new style.  Another positive effect was that some blocked issues were picked up and finished rapidly. A fresh approach! Maybe we need to change the  standup pattern every couple of iterations, just to keep the juice flowing.

Share and Enjoy:
  • Digg
  • del.icio.us
  • Google Bookmarks
  • RSS
  • Twitter

, , , ,

  1. #1 by Inanc Gumus at October 20th, 2009

    Thanks for the post. May I ask you to provide more explanation? For example: How this is different from: “one member is asking another, what’s up?”. Is the whole team makes the difference?

(will not be published)
  1. No trackbacks yet.