Stand-up Meeting

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.

Notable examples

By tradition, the Privy Council of the United Kingdom meets standing.

Software development

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.

Team members may sometimes ask for short clarifications and make brief statements, such as "Let's talk about this more after the meeting", but the stand-up does not usually consist of full-fledged discussions.

The meetings are usually timeboxed to between 5 and 15 minutes, and take place with participants standing up to remind people to keep the meeting short and to-the-point.
The stand-up meeting is sometimes also referred to as the "stand-up" when doing extreme programming, "morning rollcall" or "daily scrum" when following the scrum framework.

In Scrum

Scrum has daily meetings (the ''daily scrum'') for the team to reflect and assess progress towards the ''sprint goal''. This meeting is intended to be brief – less than 15 minutes – so any in-depth discussions about impediments are deferred until after the event is complete. As some teams conduct their meetings standing up, they may refer to this event as the "daily standup".

The older Scrum Guide (2017) suggested team members briefly (a maximum of one minute per team member) address three questions as input to this planning:

# What did I do yesterday that helped the development team meet the sprint goal?
# What will I do today to help the development team meet the sprint goal?
# Do I see any impediment that prevents me or the development team from meeting the sprint goal?

(These questions were removed from the 2020 Scrum Guide)

Whereas Kanban-style daily stand-ups focus more on:

# What obstacles are impeding my progress?
# (looking at the board from right to left) What has progressed?

See also

* Lean software development
* Five Ws

Citations

References

*

External links

*
A pocket guide for effective stand-up meetings
'


Jason Yip
*Articl
Opening Communication within a Scrum Team
fro
Methods & Tools
* {{Cite journal, title=The daily stand-up meeting: A grounded theory study , last1=Straya , first1=Viktoria , last2=Sjøberga , first2=Dag I.K. , last3=Dybåa , first3=Tore , doi=10.1016/j.jss.2016.01.004 , volume=114 , issue=20 , pages=101–124 , journal=Journal of Systems and Software, year=2016 , hdl=11250/2478996 , s2cid=206539494 , hdl-access=free

Agile software development
Meetings