I'm planning a rewrite of my "It's Not Just Standing Up" paper ("It's Still Not Just Standing Up") and one key difference is that I want to focus on the "walk the board" or "story-focused" style standups more.
If you've tried this "new style" of standup, I'd like to talk to you about it. Post a comment here or e-mail me at j.c.yip@computer.org.
How does it compare to the 3 questions style? Quickness, energy, supportiveness, self-organisation?
What is better? What is worse? Any key points or gotchas?
In case you don't know what I mean by "walk the board" standup, here are a few references:
- http://www.exampler.com/blog/2007/11/06/latour-3-anthrax-and-standups/
- http://agile-commentary.blogspot.com/2009/04/walking-board.html
- http://www.skorks.com/2009/07/stopping-people-from-switching-off-during-standups/
- http://www.infoq.com/news/2009/04/large-team-standups
- http://agile.dzone.com/news/alternative-format-daily-stand
5 comments:
We've evolved a two-part standup at our startup, which makes a social web app and practices frequent deployment.
Part 1 is a quick company-wide check-in, and Part 2 is a walk-the-board with the engineering team.
In Part 2, we work from right to left, with a focus on making sure that recently deployed stories (for us: minimally marketable features), stories pending deployment, and stories in verification get a priority review to keep the runway clear for the next MMF. It works pretty well:
- produces a clear action plan and goals for the day
- keeps Work In Progress low
- avoids any congestion in the build-it/check-it/ship-it flow
Happy to chat more if it would be helpful. luke at lukemelia dot com.
Cheers,
Luke
Hadn't realized this was called walking the board. It's the style I used over the last year when I was able to do a bit of Agile for one or two smaller projects. I always liked the idea even if it gives a bit of focus to the Scrum Master.
You can find my story here:
http://agile-commentary.blogspot.com/2009/04/walking-board.html
Thanks Keven, if you follow the dzone link, it actually points to your blog entry.
Jason,
I transformed a large development project (over 100 developers/smes/qa) with a number of functional interdependencies through a walking the board type process. We changed our focus from what each individual was working on to what was needed to move the current work forward. We focused our daily stand up on collectively advancing the next MMF (although we didn't call it that). The result was a change from a blaming and plausible deniability culture to a culture of understanding and coordination. The result was a dramatic improvement in quality and velocity.
Post a Comment