Sunday, March 16, 2014

Stand Up Meetings

In software development (particularly the Agile framework) there's a meeting that occurs each day during a sprint called the stand-up (or sometimes daily scrum). This check-in is a time for the dev team to share a brief (no more than 2 minutes each) update of their progress. All team members who are physically able stand for the duration of the meeting, the idea being that a level of discomfort for standing too long will discourage meetings running over the allotted time.

Impediments / stumbling blocks are noted by the Scrum Master and a resolution is worked on outside of the meeting. At most, a team member may make a brief statement in reply, such as, "Let's connect more on that after the meeting." No detailed discussions happen during this meeting.

Other Guidelines:

  • All members of the development team come prepared with their updates.
  • Meeting always starts precisely on time, even if some team members are missing.
  • Meeting should happen at the same time and place each day.
  • Meeting is timeboxed to no more than 15 minutes
  • Anyone is welcome to attend, but only core roles speak.
Things I Like:
  • Daily collaboration among team members so everyone is aware of each other's progress.
  • 15 minute limit values each team member's time.
  • Opportunities for offline discussion, problem-solving, and establishing a thought partner when needed without the rest of the team feeling locked into the meeting.
What benefits could this have to projects and meetings you lead / are involved in? What challenges to this kind of meeting structure do you see?