Your Training Partner
Techniques Toolbox
Diagram of the Daily Scrum. On the left, what goes in: the Sprint Goal, the Sprint Backlog and the work done since the last Daily Scrum. In the centre, the Developers meet for fifteen minutes every day at the same time and place. On the right, what comes out: the plan for the next 24 hours, the adapted Sprint Backlog and the impediments to remove. An arrow leads from the meeting to the detailed discussions between the people concerned. A loop leads back to the next day.

Daily Stand-up

The daily stand-up is a fifteen-minute meeting that the team holds every working day at the same time and place. The people who do the work of the iteration inspect their progress toward the shared goal and plan the next 24 hours of work. The Scrum Guide calls this event the Daily Scrum and reserves it for the Developers. The Guide sets the length, the purpose and the output of the event: a plan for the next day of work. The Developers choose its structure.

Goal

Every day, the team checks at the daily stand-up that the work in progress leads to the Sprint Goal. It then replans the next 24 hours. The Scrum Guide makes this the purpose of the Daily Scrum. It adds that the Developers adapt the Sprint Backlog as necessary. The Sprint Goal is the single objective that the Developers commit to reaching. The Sprint Backlog holds this goal, the Product Backlog items selected for the Sprint and the plan for delivering them. According to the Guide, the meeting improves communication, identifies impediments, speeds up decisions and removes the need for other meetings.

Jason Yip names the problems that the meeting addresses when a group tries to work as a team. The meeting helps the team to share an understanding of its goals, to coordinate its efforts, to share problems and improvements and to identify as a team. The Agile Alliance gives the reason: without an explicit occasion to share recent information, critical knowledge can fall through the cracks.

The meeting produces a plan for the next day of work.

The Daily Scrum within the Sprint. The Developers inspect their progress toward the Sprint Goal and leave with the plan for the next 24 hours. They meet again during the day for the detailed discussions.

Daily Scrum, daily stand-up and the three questions

Both names refer to the same meeting. The Agile Alliance traces "daily stand-up" to Extreme Programming, which recommended standing up. The Scrum Guide never mentions standing.

According to Jeff Sutherland, the first Scrum team adopted the daily meeting at Easel Corporation in 1993. The team had just read James Coplien's study of Borland's Quattro Pro team. Starting in its first sprint, it asked three questions: what did I do yesterday, what will I do today, what is in my way. The Scrum Primer by Pete Deemer and Gabrielle Benefield set the classic form. Each member answers the three questions and only those.

The 2017 Scrum Guide gave the three questions as an example of structure. It tied each one to the Sprint Goal: "What did I do yesterday that helped the Development Team meet the Sprint Goal?" According to the Guide's revisions page, this wording puts the team before the individual. It counters a failure mode of the round-the-table format that Jason Yip also describes.

The 2020 Guide removed the three questions and lets the Developers choose the structure and techniques. The revisions page gives the reason under the heading Even Less Prescriptive: the new version removes or softens prescriptive language. The Guide sets two conditions: the meeting focuses on progress toward the Sprint Goal and produces a plan for the next day of work. The three questions remain an option.

PMI's PMBOK Guide calls this meeting a daily coordination meeting. It describes it with the three questions that the 2020 Scrum Guide removed: the team reviews the previous day's progress, states its intentions for the day and raises impediments. The meeting usually lasts fifteen minutes or less. A project manager who runs a hybrid project often meets this version.

Usage

When to use it

  • A team that works toward a shared iteration goal: synchronise the work every day before gaps build up.
  • Interdependent tasks spread across several people: decide every day who takes what and who helps whom.
  • A Scrum Team: the Daily Scrum is a Scrum event held on every working day of the Sprint.
  • A team spread across several sites: each member sends written answers before the daily call.
  • Stakeholders who follow the work day by day: they observe the meeting instead of calling one more meeting.

When not to use it

  • Work without interdependencies: there is nothing to coordinate every day; a weekly check-in is enough.
  • A progress report expected by management: the meeting serves the team; show overall progress on a visible burndown chart or at the Sprint Review.
  • Several teams on one product: a joint meeting soon runs past fifteen minutes; each team holds its own and a Scrum of Scrums coordinates the dependencies.

Description

What the Scrum Guide sets and what practice adds

The Guide sets few rules. Most stand-up habits come from the Scrum Primer, the Agile Alliance or Jason Yip.

AspectScrum Guide 2020Common practice and its source
LengthFifteen minutes.Stand up to keep to the time (Extreme Programming according to the Agile Alliance; Scrum Primer).
Time and placeSame time and place on every working day of the Sprint.Start on time without waiting for latecomers (Yip). Meet in front of the team's board (Agile Alliance, Yip).
ParticipantsThe Developers. The Product Owner and the Scrum Master take part as Developers if they work on Sprint Backlog items.No manager. A stakeholder offers help after the meeting (Scrum Primer). Observers who know the rules (Yip).
StructureThe Developers' choice.The three questions (Scrum Primer). Walking the board (Yip).
DiscussionThe Developers often meet during the day to adapt the plan.No discussion during the meeting. A follow-up meeting straight after (Scrum Primer). Topics noted on a parking lot (Agile Alliance).
OutputA plan for the next day of work.Impediments noted and handed to the Scrum Master (Scrum Primer).
FacilitationThe Scrum Master makes sure that the event takes place and stays within its timebox.Facilitation rotates among the members (Yip).
What the 2020 Scrum Guide sets, what practice adds and the source of each practice.

Preparing the meeting

The team picks a time and a place and keeps to them. The Guide gives the reason for the regularity: a fixed time and place reduce complexity. Yip advises starting on time without waiting for latecomers, including architects and managers. Repeated lateness often signals a badly chosen time or place. The team then moves the meeting.

When a flexitime team holds the meeting at the start of its core hours, the meeting sets the focus for the day. Yip names the downside: some people wait for the meeting before they start work. If it falls late in the morning, this wait costs hours of work. The team then schedules it far enough into the day that it no longer marks the start of work.

The Guide asks for a Sprint Backlog detailed enough for the Developers to inspect their progress in the Daily Scrum. An item that is too large stays "in progress" for days and says nothing about its progress. The team splits it in backlog refinement before the Sprint. According to the Guide, the Developers often break items down at Sprint Planning into tasks of one day or less. Such a task changes state between two Daily Scrums.

A distributed team holds the meeting on a video call in front of a shared board. At SirsiDynix, teams split between Provo and St Petersburg met every day at 7:45 Utah time, which was 17:45 in St Petersburg. Each member sent written answers before the call. According to Sutherland, the written answers shortened the call and removed part of the language barrier. The same practice serves a Swiss team that mixes French and German speakers.

Choosing a structure

Round the table and the three questions

Each member in turn says what they have finished since yesterday, what they will do today and what is blocking them. Yip sees this as the minimum information that serves the goals of the meeting. He also names its failure mode: the meeting centres on personal commitment. Everyone shows that they are busy. Nobody says whether the item they work on is getting close to "done". Yip calls this smell Focused on the Runners, not the Baton. He proposes asking the three questions from the point of view of the work item rather than the person (Work Items Attend). This variant leads to walking the board.

The team settles the speaking order without the facilitator. According to Yip, a facilitator who decides who speaks works against self-organisation. He proposes rules: speak in turn in a fixed order, toss an object that gives the floor, draw a numbered card on arrival or let the last arrival speak first.

Walking the board

The team goes through the items on its board instead of giving the floor to each person. Yip calls this structure Walk the Board. The team reads the columns from right to left and each column from top to bottom: the item closest to "done" comes first. The people who work on an item speak about it once and in full. Yip quotes the default sequence that Pawel Brodzinski proposes: blocked items, urgent items, items that have not moved since the last meeting, then everything else by priority.

The same work read in two ways. Going round the table, each person talks about their own tasks and a shared item comes up twice. Walking the board, the team reads the items from right to left and from top to bottom: it discusses each item once. Card E, which nobody holds, appears only on the board.

This structure needs a board. The task board is its simplest form. According to Yip, a team that walks the board without rotating the facilitator tends to report to whoever holds the board.

Keeping to fifteen minutes

The team keeps to fifteen minutes if it moves discussion to after the meeting. The Scrum Primer sends every discussion to a follow-up meeting of the people concerned straight after. The Agile Alliance puts each discussion topic on a parking lot list. The team takes these topics up after the meeting. Yip proposes that the team agree on a short phrase such as "take it offline". With Benjamin Mitchell's two-hands rule, a person raises a hand when the conversation drifts off topic. As soon as a second hand goes up, the conversation stops and resumes after the meeting.

Yip separates the clarifying question from problem solving. Information that a participant has not understood is useless: the question that clarifies it stays in the meeting.

According to the Guide, the Developers often meet during the day to adapt or replan the rest of the Sprint. A meeting that overruns every day often signals a team whose members wait for the morning meeting to talk.

Closing on the plan for the next 24 hours

The meeting ends when each Developer knows what they will do until the next Daily Scrum and with whom. The Developers alone change the work plan. If they can no longer deliver an item as planned, they negotiate the scope of the Sprint Backlog with the Product Owner; the Sprint Goal does not change.

At the end of the meeting, each impediment has an owner. The Guide makes the Scrum Master responsible for causing the removal of the team's impediments. Yip advises posting them on an impediment board with the number of occurrences and the status of each. In his view, apart from a culture of blame, nothing stops people raising impediments more surely than impediments that nobody removes. He also advises signalling the end of the meeting with an agreed phrase or gesture.

Who facilitates the meeting

The Guide gives the meeting to the Developers. The Scrum Master makes sure that it takes place, stays productive and keeps within its timebox. The Guide does not put the Scrum Master in charge of running it. The 2017 Guide said so: the Development Team is responsible for conducting the Daily Scrum. Yip recommends rotating the facilitator among the members, then doing without one. A team new to stand-ups benefits from a coach at the start.

The 2017 Guide made the Daily Scrum an internal meeting for the Development Team: if others are present, the Scrum Master ensures that they do not disrupt it. The Scrum Primer advises against a manager attending: the team feels watched, believes it must report major progress every day and keeps quiet about its problems. It advises a stakeholder to offer the team help with removing impediments after the meeting. Yip accepts observers if they know the rules of the meeting.

In the Guide, the Developers are the people in the Scrum Team who are committed to creating any aspect of the Increment. A business analyst in the Scrum Team is therefore a Developer in the Guide's sense and takes part in the meeting. In the meeting, the analyst raises an unresolved business rule or a question that waits on a stakeholder. The analyst looks for the answer with the person concerned after the meeting.

Signs of a drifting meeting

According to Yip, the absence of symptoms does not prove that the meeting works.

SymptomWhat you seeRemedy
Reporting to the leaderEveryone speaks while looking at the manager or the facilitator. The Agile Alliance calls it "perhaps the most common mistake": the meeting turns into a status report.Rotate the facilitator. The facilitator breaks eye contact with the speaker. An object passes from hand to hand.
Storytelling and problem solvingOne person recounts an incident in detail. Two others look for the solution on the spot. The meeting drags on."Take it offline". A follow-up meeting of the people concerned.
Focused on the runners, not the batonEveryone shows that they are busy. Nobody says whether an item is moving.Walk the board item by item.
Impediments not raisedNobody raises an impediment although the team delivers little. The Agile Alliance speaks of a "no problem" meeting.Impediment board. A retrospective to look for the cause.
Impediments never removedThe same impediment comes back every day.Public tracking on the impediment board.
LatenessMembers arrive late and the meeting waits for them.Start on time. Revisit the time or the place.
The symptoms of a drifting meeting and their remedies as Jason Yip and the Agile Alliance describe them.

The "no problem" meeting sometimes comes from the culture. The Agile Alliance reads it as the sign of an organisation where people are uncomfortable discussing difficulties in a group. In a team where admitting a delay costs dearly, everyone hides delays in the meeting, whatever the structure.

AI considerations

A language model prepares the meeting from the backlog tool. It sorts the items on the board in Brodzinski's order. The team gets a starting point for walking the board. In a distributed team, the model collects the written answers sent before the call and translates them between French and German.

A tool cannot tell whether progress serves the Sprint Goal. An item can change column without bringing the team closer to its goal. The plan for the next 24 hours remains the Developers' decision. A generated summary passed on to the manager brings back the status report that the technique sets aside. The team soon notices and stops raising its impediments.

If the team records and transcribes the meeting, it processes personal data within the meaning of the Federal Act on Data Protection (FADP). What people say concerns named persons, their delays and their difficulties. The written answers that the model translates carry the same kind of personal data: if the team sends them to an external model, it also processes personal data. Before any recording, the team decides what is kept, by whom and for how long.

Examples

The team in this example records the plan in its backlog tool. It builds the customer portal of a pension fund in ten-day Sprints. The Sprint Goal is that insured members download their 2026 pension certificate from the portal. The meeting takes place on the morning of the sixth day.

Sprint Backlog itemProgress toward the goalNext 24 hoursImpediment and follow-up
PDF generation of the certificateFinished yesterday. Checked on 20 test files.Luca joins Nadia on the download button.None.
Display of the retirement savingsBlocked: the 2026 interest rate is missing in the test environment.Sofia finishes the layout with a dummy rate.The Scrum Master asks the Data team for access to the rate table. Follow-up at 9:30 between Sofia and Marc (business analyst) on the rounding rule.
Download button in the customer portalNot started. Five days left including today.Nadia and Luca pair on it from this morning.Task added to the Sprint Backlog: accessibility test of the button.
Email notice to the insured memberNot started. Not needed to reach the goal.Nobody.This afternoon Marc proposes to the Product Owner that the team drop it from the Sprint Backlog.
The plan for the next 24 hours on the morning of the sixth day of a ten-day Sprint. The Developers add a task to the Sprint Backlog and propose to the Product Owner that the team drop one item from the Sprint Backlog; the Sprint Goal does not change.

The Scrum Master takes on the impediment in the second row. Sofia and Marc discuss the rounding rule at 9:30 in a follow-up meeting.

Visualisations

The daily loop shows what goes into the meeting and what comes out of it. It places the detailed discussions outside the meeting. The speaking-order diagram contrasts the two structures: going round the table follows the people, walking the board follows the work.

In the Examples, a table shows the plan for the next 24 hours.

Cost

PhaseLevelJustification
PreparationLowThe team sets the time and the place once. Each member updates their cards before the meeting.
ExecutionMediumFifteen minutes per working day for the whole team, that is 17.5 person-hours over a ten-day Sprint for seven Developers.
DocumentationLowThe plan for the next 24 hours fits in the Sprint Backlog. The meeting produces no minutes.

Tooling

A physical board is enough for a co-located team. The Agile Alliance glossary advises holding the meeting near the task board. Yip recommends meeting where the work happens rather than in a meeting room.

Backlog management tools (Jira, Azure DevOps, GitLab and their equivalents) display the board of a distributed team. Each member moves their cards there before the meeting: the team reads the state of the work instead of typing it in.

A video-conferencing tool (Teams, Zoom, Webex) carries the remote meeting and shares the board on screen. A messaging channel collects the written answers of a distributed team before the call. A visible timer helps a team that overruns. Yip advises timing the meetings while their length is a problem, then stopping.

Sources

  • Ken Schwaber and Jeff Sutherland, The Scrum Guide, November 2020, sections "Daily Scrum", "Scrum Team", "Developers", "Scrum Master", "Sprint Planning", "Sprint Backlog" and "Commitment: Sprint Goal": the purpose of the Daily Scrum, its length, its time and place, its participants, the structure left to the Developers, the plan for the next day of work, the stated benefits, the adjustments to the plan during the day, the breakdown into tasks of one day or less, the negotiation of scope with the Product Owner and the role of the Scrum Master toward the events and the impediments.
  • Ken Schwaber and Jeff Sutherland, The Scrum Guide, November 2017, section "Daily Scrum": the three questions given as an example of structure, the Development Team conducting the meeting and the meeting as internal to that team.
  • Scrum Guide Revisions, "Changes between 2017 and 2020 Scrum Guides": the removal of the Daily Scrum questions in 2020 for a less prescriptive Guide. "Changes between 2016 and 2017 Scrum Guides": the rewording of the questions around the team.
  • Jeff Sutherland, The Scrum Papers: Nut, Bolts, and Origins of an Agile Framework, 30 March 2021: the adoption of the meeting by the first Scrum team at Easel Corporation in 1993 and the three questions of its first sprint ("Dedication" and "Agile Development: Lessons Learned from the First Scrum"). The classic form of the Scrum Primer by Pete Deemer and Gabrielle Benefield and the help that stakeholders offer after the meeting ("Scrum Primer Version 1.2"). The daily call at SirsiDynix prepared in writing ("Distributed Scrum: Agile Project Management with Outsourced Development Teams").
  • Jason Yip, It's Not Just Standing Up: Patterns for Daily Standup Meetings, martinfowler.com, version of 21 February 2016: the problems that the meeting addresses, the structures, the speaking order, the time and place, the length, the rotating facilitator and the symptoms of a drifting meeting.
  • Agile Alliance, Agile Glossary: Daily Meeting: the names of the meeting and the origin of the name stand-up, the parking lot, the task board as the place of the meeting and the common pitfalls.
  • Project Management Institute, A Guide to the Project Management Body of Knowledge (PMBOK Guide), 8th ed., PMI, Section 5, "Daily coordination meeting": the daily coordination meeting, its three questions and its length.
Cynefin
All techniques
Darnall-Preston Complexity Index