Search The Blog
Latest Posts
Twitter: @RoyOsherove
About this site

TDD in .NET Online Course

TDD and BDD in Ruby Online Course



This site aims to connect all the dots of my online activities - from tools, books blogs and twitter accounts, to upcoming conferences, engagements and user group talks.

« The Art Of Unit Testing - Starting out My First Book | Main | Cool Tool: Direct Access - Keyboard macros everywhere »

It's Not Just Standing Up: Patterns for Daily Stand-up Meetings

Martin Fowler (a.k.a "The GoF dude")(I messed up and confused Martin as one of the authors. I tend to do that a lot - think that Martin has done lots and lots of things.. thanks for the comments.) points to an interesting article about Stand-up meeting patterns:

It's Not Just Standing Up: Patterns for Daily Stand-up Meetings

"...he discusses how make stand-up meetings work. Stand-ups (also known as scrums) are short daily status meetings used to communicate what everyone is doing to everyone else. When they work well, they can be very effective - so it's good to know the tips that make them work."


Couldn't have said it better myself.

Here are some of the "patterns" described, and I'll note that from my reading, some of them are not really patterns for the whole meetings, but "best practices" to be carried out during the meeting, rather than describing "different kinds" of stand up meetings (though a couple actually do change the meaning of the meeting, most of them simply add value to it):


  • Same Place, Same Time
  • Pig and Chickens
  • All Hands
  • Attend By Proxy
  • Use the Stand-up to Start The Day
  • Don't Use the Stand-up to Start the Day
  • Huddle
  • Fifteen Minutes or Less
  • Stand Up
  • Round Robin
  • Time the Meetings
  • Yesterday Today Obstacles
  • Focus on the Backlog
  • Take It Offline
  • Blockage Board Rotate the Facilitator
  • Plus Various Smells

PrintView Printer Friendly Version

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>
Web Analytics