Stand and Deliver: Why I Hate Stand-Up Meetings

ABSTRACT

Stand-up meetings are an important component of the “whole team,” which is one of the fundamental practices of extreme programming (XP).

According to the Extreme Programming Web site, the stand-up meeting is one part of the rules and practices of extreme programming: “Communication among the entire team is the purpose of the stand-up meeting. They should take place every morning in order to communicate problems, solutions, and promote team focus. The idea is that everyone stands up in a circle in order to avoid long discussions. It is more efficient to have one short meeting that everyone is required to attend than many meetings with a few developers each.” [1]

REFERENCES

• 1: 1. Extreme Programming: see http://www.extremeprogra mming.org/rules/standupmeeting.html.
• 2: 2. Extreme Programming: see http://www.extremeprogra mming.org/rules/standupmeeting.html.
• 3: Jonathan Rasmusson, Introducing XP into Greenfield Projects: Lessons Learned, IEEE Software, v.20 n.3, p.21-28, May 2003 [doi>10.1109/MS.2003.1196316]
• 4: Laurie Williams, Guest Editor's Introduction: The XP Programmer—The Few-Minutes Programmer, IEEE Software, v.20 n.3, p.16-20, May 2003 [doi>10.1109/MS.2003.1196315]
• 5: 5. Twelve|71: see http://www.twelve71.com/xp/ standup.jsp.

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.9 Management
          Subjects: Programming teams

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.1 Requirements/Specifications
          Subjects: Elicitation methods (e.g., rapid prototyping, interviews, JAD)
      D.2.9 Management
          Subjects: Software process models (e.g., CMM, ISO, PSP); Productivity

General Terms:
Human Factors, Management, Standardization