Concept

Stand-up meeting

Summary
A stand-up meeting (stum) is a meeting in which attendees typically participate while standing. The discomfort of standing for long periods is intended to keep the meetings short. By tradition, the Privy Council of the United Kingdom meets standing. According to the PMBOK (7th edition) by the Project Management Institute (PMI), daily standup is a "brief, daily collaboration meeting in which the team review progress from the previous day, declares intentions for the current day, and highlights any obstacles encountered or anticipated." Some software development methodologies envision daily team meetings to make commitments to team members. The daily commitments allow participants to know about potential challenges as well as to coordinate efforts to resolve difficult or time-consuming issues. The stand-up has particular value in agile software development processes, such as scrum or Kanban, but can be utilized in context of any software-development methodology. The meeting should usually take place at the same time and place every working day. All team members are encouraged to attend, but the meetings are not postponed if some of the team members are not present. One of the crucial features is that the meeting is a communication opportunity among team members and not a status update to management or stakeholders. Although it is sometimes referred to as a type of status meeting, the structure of the meeting is meant to promote follow-up conversation, as well as to identify issues before they become too problematic. The practice also promotes closer working relationships in its frequency, need for follow-up conversations and short structure, which in turn result in a higher rate of knowledge transfer – a much more active intention than the typical status meeting. Team members take turns speaking, sometimes passing along a token to indicate the current person allowed to speak. Each member talks about progress since the last stand-up, the anticipated work until the next stand-up and any impediments, taking the opportunity to ask for help or collaborate.
About this result
This page is automatically generated and may contain information that is not correct, complete, up-to-date, or relevant to your search query. The same applies to every other page on this website. Please make sure to verify the information with EPFL's official sources.
Related courses (2)
MICRO-371: Software architecture
Ce cours couvre des sujets liés à l'architecture software moderne et industrielle : la gestion agile de projets, la spécification des besoins, le développement d'applications critiques, la programmat
MGT-489: Project management & collaboration
This course is dedicated to integrating 1) a project thinking mindset, by mastering what needs to be ensured for any project to be carried out in the most favorable conditions, and 2) practice collabo
Related lectures (9)
Software Development Process
Explores Scrum, the waterfall model, teamwork, code reviews, and asynchronous software design in software development.
Software Development Processes: Agile Methods
Explores software development processes, comparing Waterfall model with Agile methods, focusing on Scrum, values, principles, and team roles.
Global Health Issues: Challenges and Ethics
Explores global health challenges, ethics, and regenerative medicine interdisciplinary aspects.
Show more
Related publications (3)

Neuroprosthetic technologies to augment the impact of neurorehabilitation after spinal cord injury

Silvestro Micera, Grégoire Courtine, Jocelyne Bloch, Eduardo Martin Moraud, Joachim von Zitzewitz, Nicolas Francis Fumeaux, Marco Capogrosso, Rubia van den Brand, Fabien Bertrand Paul Wagner, Jean-Baptiste Mignardot

Spinal cord injury leads to a range of disabilities, including limitations in locomotor activity, that seriously diminish the patients’ autonomy and quality of life. Electrochemical neuromodulation therapies, robot-assisted rehabilitation and willpower-bas ...
2015

Finding Information in Multimedia Meeting Records

Hervé Bourlard, Andrei Popescu-Belis

This paper surveys the work carried out within two large consortia, AMI and IM2, on improving access to records of human meetings thanks to multimodal interfaces called meeting browsers. These tools help users navigate through multimedia records containing ...
2012

Finding Information in Multimedia Records of Meetings

Hervé Bourlard, Andrei Popescu-Belis

This paper overviews the work carried out within two large consortia on improving the access to records of human meetings using multimodal interfaces. The design of meeting browsers has emerged as an important goal, with both theoretical interest and pract ...
Idiap2011
Related concepts (4)
Software development process
In software engineering, a software development process is a process of planning and managing software development. It typically involves dividing software development work into smaller, parallel, or sequential steps or sub-processes to improve design and/or product management. It is also known as a software development life cycle (SDLC). The methodology may include the pre-definition of specific deliverables and artifacts that are created and completed by a project team to develop or maintain an application.
Timeboxing
In agile principles, timeboxing allocates a maximum unit of time to an activity, called a timebox, within which planned activity takes place. It is used by agile principles-based project management approaches and for personal time management. Timeboxing is used as a project planning technique. The schedule is divided into a number of separate time periods (timeboxes), with each part having its own deliverables, deadline and budget. Sometimes referred to as schedule as independent variable (SAIV).
Lean software development
Lean software development is a translation of lean manufacturing principles and practices to the software development domain. Adapted from the Toyota Production System, it is emerging with the support of a pro-lean subculture within the agile community. Lean offers a solid conceptual framework, values and principles, as well as good practices, derived from experience, that support agile organizations. The expression "lean software development" originated in a book by the same name, written by Mary Poppendieck and Tom Poppendieck in 2003.
Show more