Stand-up meeting

Last updated

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.

Contents

Notable examples

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

Software development

Definition

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." [2]

Description

A stand-up meeting Daily sprint meeting.jpg
A stand-up meeting

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, [3] [4] 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. [5] 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. [6] 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. [7]

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.[ citation needed ]

Timeboxed

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. [6] 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.

Three questions

Scrum has daily meetings (the daily scrum) for the team to reflect and assess progress towards the sprint goal. [8] 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:

  1. What did I do yesterday that helped the development team meet the sprint goal?
  2. What will I do today to help the development team meet the sprint goal?
  3. 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:

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

See also

Citations

  1. ↑ "Privy Council Office FAQs". Privy Council Office. Retrieved 17 May 2016.
  2. ↑ Project Management Institute 2021, Glossary §3 Definitions.
  3. ↑ "Agile Testing". Borland.com. Archived from the original on 2012-07-06. Retrieved 2010-01-27.
  4. ↑ "Agile Stand-up on Agile Testing". Borland.com. Archived from the original on January 12, 2010. Retrieved 2010-01-27.
  5. ↑ Stray, Viktoria; Sjøberg, Dag; Dybå, Tore (2016-01-11). "The daily stand-up meeting: A grounded theory study". Journal of Systems and Software. 114 (20): 101–124. doi:10.1016/j.jss.2016.01.004. hdl: 11250/2478996 . S2CID   206539494.
  6. 1 2 "It's Not Just Standing Up". Martin Fowler.
  7. ↑ "Daily Scrum Meetings". Mountain Goat Software.
  8. ↑ "Scrum Guide". scrum.org.

Related Research Articles

In software development, a lead programmer is responsible for providing technical guidance and mentorship to a team of software developers. Alternative titles include development lead, technical lead, lead programmer, or lead application developer. When primarily contributing a low-level enterprise software design with focus on the structure of the app, e.g. design patterns, the role would be a software architect

Agile software development is the mindset for developing software that derives from values agreed upon by The Agile Alliance, a group of 17 software practitioners in 2001. As documented in their Manifesto for Agile Software Development the practitioners value:

In agile principles, timeboxing allocates a maximum unit of time to an activity, called a timebox, within which a planned activity takes place. It is used by agile principles-based project management approaches and for personal time management.

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.

Agile management is the application of the principles of Agile software development and Lean Management to various management processes, particularly product development. Following the appearance of The Manifesto for Agile Software Development in 2001, Agile techniques started to spread into other areas of activity. The term Agile originates from Agile manufacturing - which in the early 1990s had developed from flexible manufacturing systems and lean manufacturing/production.

<span class="mw-page-title-main">Scrum (software development)</span> Management framework

Scrum is an agile team collaboration framework commonly used in software development and other industries.

<span class="mw-page-title-main">Jeff Sutherland</span> American computer scientist

Jeff Sutherland is one of the creators of Scrum, a framework for product management. Together with Ken Schwaber, he presented Scrum at OOPSLA'95. Sutherland contributed to the creation of the Agile Manifesto in 2001. Along with Ken Schwaber, he wrote and maintains The Scrum Guide, which contains the official definition of the framework.

<span class="mw-page-title-main">Burndown chart</span> Diagram of work left versus time

A burndown chart or burn down chart is a graphical representation of work left to do versus time. The outstanding work is often on the vertical axis, with time along the horizontal. A burn down chart is a run chart of remaining work. It is useful for predicting when all of the work will be completed. It is often used in agile software development methodologies such as Scrum. However, burn down charts can be applied to any project containing measurable progress over time.

In software engineering, a software development process or software development life cycle (SDLC) 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. 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.

Lean project management is the application of lean concepts such as lean construction, lean manufacturing and lean thinking to project management.

<span class="mw-page-title-main">Mike Cohn</span> American software developer (born 1962)

Mike Cohn is one of the contributors to the Scrum software development method. He is one of the founders of the Scrum Alliance.

A programming team is a team of people who develop or maintain computer software. They may be organised in numerous ways, but the egoless programming team and chief programmer team have been common structures.

<span class="mw-page-title-main">Kanban (development)</span> Software development methodology

Kanban is a lean method to manage and improve work across human systems. This approach aims to manage work by balancing demands with available capacity, and by improving the handling of system-level bottlenecks.

<span class="mw-page-title-main">Kanban board</span> Main tool used to implement the kanban project management methodology

A kanban board is one of the tools that can be used to implement kanban to manage work at a personal or organizational level.

<span class="mw-page-title-main">Cumulative flow diagram</span>

A cumulative flow diagram is a tool used in queuing theory. It is an area graph that depicts the quantity of work in a given state, showing arrivals, time in queue, quantity in queue, and departure.

Disciplined agile delivery (DAD) is the software development portion of the Disciplined Agile Toolkit. DAD enables teams to make simplified process decisions around incremental and iterative solution delivery. DAD builds on the many practices espoused by advocates of agile software development, including scrum, agile modeling, lean software development, and others.

eXtreme Manufacturing (XM) is an iterative and incremental framework for manufacturing improvement and new product development that was inspired by the software development methodology Scrum and the systematic waste-elimination (lean) production scheduling system Kanban(かんばん ).

Scrumban is an Agile aligned approach to product delivery which is a hybrid of Scrum and Kanban. Scrumban was originally designed as a way to transition from Scrum to Kanban.

The scaled agile framework (SAFe) is a set of organization and workflow patterns intended to guide enterprises in scaling lean and agile practices. Along with disciplined agile delivery (DAD) and S@S (Scrum@Scale), SAFe is one of a growing number of frameworks that seek to address the problems encountered when scaling beyond a single team.

Agile learning generally refers to the transfer of agile methods of project work, especially Scrum, to learning processes. Likewise, agile learning proceeds in incremental steps and through an Iterative design which alternates between phases of learning and doing. The tutors rather have the role of a learning attendant or supporter. In a narrower sense, it is intended to allow competence-oriented, media-based learning in the work process within companies. In addition, the term can take several other meanings and is also often used within e-learning and online environments.

References

This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.