Abstract
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. Extreme Programming: see http://www.extremeprogra mming.org/rules/standupmeeting.html.Google Scholar
- 2. Extreme Programming: see http://www.extremeprogra mming.org/rules/standupmeeting.html.Google Scholar
- 3. Rasmusson, Jonathan. Introducing XP into Greenfield projects: Lessons learned, IEEE Software (May-June 2003), 21-28. Google ScholarDigital Library
- 4. Williams, Laurie. "The XP programmer: The four-minute programmer," IEEE Software (May-June 2003), 16-20. Google ScholarDigital Library
- 5. Twelve|71: see http://www.twelve71.com/xp/ standup.jsp.Google Scholar
Index Terms
- Stand and Deliver: Why I Hate Stand-Up Meetings: Stand-up meetings are an important component of the ’whole team’, which is one of the fundamental practices of extreme programming (XP).
Recommendations
Planned and unplanned meetings in large-scale projects
XP '18: Proceedings of the 19th International Conference on Agile Software Development: CompanionTo succeed with large-scale projects, teams need to coordinate ideas and efforts, which is a core purpose of meetings. We conducted a case study in a large software company where we observed meetings and surveyed 65 members working in large-scale agile ...
The daily stand-up meeting
The first study fully devoted to the daily stand-up meeting in agile projects is reported.Data from interviews with 60 people and observations of 79 daily stand-up meetings.Benefits include information sharing and opportunity to discuss and solve ...
A methodological leg to stand on: lessons learned using grounded theory to study software development
CASCON '08: Proceedings of the 2008 conference of the center for advanced studies on collaborative research: meeting of mindsWe are engaged in a qualitative research project to understand how people manage the process of software development. This study uses grounded theory as its method of inquiry and we have learned much about what is and what is not a grounded theory. We, ...
Comments