Daily Standup
What is Daily Standup?
A daily standup is a team's brief daily check-in, usually 15 minutes, to review progress toward the current goal, raise blockers and adjust the next day's plan. Scrum calls it the Daily Scrum.
Updated November 2026 · 3 min read
A daily standup is a short meeting, usually 15 minutes, in which a team checks progress toward its current goal, surfaces anything blocking the work and adjusts the plan for the next day. The name comes from the practice of standing up during the meeting to keep it brief. In Scrum the same event is called the Daily Scrum, and many teams outside software, including marketing, operations and support teams, now hold their own version.
The value of a standup is not the status report. It is the chance to spot problems while they are still small: two people working on overlapping changes, a task stuck waiting on another team, or a goal that is drifting out of reach. A good standup ends with people knowing who needs to talk to whom after the meeting.
Origins and the Scrum guide definition
Stand-up meetings appear in both Scrum and Extreme Programming from the 1990s. The Scrum Guide defines the Daily Scrum as a 15-minute event for the Developers, held at the same time and place every working day, whose purpose is to inspect progress toward the sprint goal and adapt the sprint backlog as needed. Earlier editions of the guide suggested three questions for each person: what did I do yesterday, what will I do today, and what is in my way. The 2020 edition dropped the questions and leaves the format to the team, as long as the meeting stays focused on the goal.
Common standup formats
- Three questions. Each person answers yesterday, today and blockers. Easy to start with, but it tends to turn into individual status reports.
- Walk the board. The team goes through its task board from right to left, starting with the items closest to done, and asks what it would take to finish each one. This keeps attention on flow rather than on people.
- Goal-first. The team starts by asking whether it is still on track for the sprint goal, then discusses only the work that affects that answer.
- Asynchronous. Distributed teams across time zones post written updates in a shared channel or tool, and meet live only when a blocker needs discussion.
How to run an effective standup
- Keep the same time and place. Predictability removes scheduling overhead and makes attendance a habit.
- Hold it in front of the work. Use the physical or digital board so updates refer to real items, not memory. A visible board works as an information radiator.
- Stop at 15 minutes. If a topic needs more, note it and hold a follow-up with only the people involved.
- Name blockers precisely. "Waiting on the API team to approve the schema change" is actionable; "some issues with the API" is not.
- Let the team own it. A Scrum Master or lead may facilitate at first, but the meeting is for the people doing the work, not a report to a manager.
The cost of a standup: A hypothetical example
Consider a hypothetical team of seven developers whose standup has crept to 30 minutes because it has become a problem-solving session. That costs 7 × 30 = 210 person-minutes a day, or 1,050 person-minutes (17.5 hours) over a five-day week.
The team switches to walking the board, caps the meeting at 15 minutes and moves detailed discussions to short follow-ups with only the two or three people who need to be there. The standup now costs 7 × 15 = 105 person-minutes a day, or 525 person-minutes (8.75 hours) a week, saving 8.75 hours of team time each week. The follow-ups take some of that time back, but they involve fewer people, and the developers who are not needed return to their work.
Common pitfalls
- Reporting to the manager. When everyone faces the lead and recites their tasks, the meeting becomes status theater. Updates should be addressed to teammates.
- Solving problems in the meeting. Long technical discussions keep the whole team waiting. Flag the issue and take it offline.
- Ignoring the goal. A standup that never mentions the sprint goal cannot tell the team whether it is on track.
- Letting blockers sit. If the same blocker is reported three days in a row, the meeting is not working. Assign an owner to remove it the day it is raised.
- Skipping it when busy. The days with the most pressure are the days coordination matters most.
The daily standup is one of the core agile ceremonies, alongside sprint planning and the sprint retrospective. Large programs often add a scrum of scrums so that blockers between teams get the same daily attention.
Frequently asked questions
How long should a daily standup last?
A daily standup should last about 15 minutes, which is also the timebox the Scrum Guide sets for the Daily Scrum. If a topic needs more time, note it and hold a follow-up with only the people involved. A standup that creeps to 30 minutes for a team of seven costs about 17.5 person-hours a week.
What are the three daily standup questions?
The classic daily standup questions are what did I do yesterday, what will I do today and what is in my way. Earlier editions of the Scrum Guide suggested them, but the 2020 edition dropped them and leaves the format to the team. Many teams now walk the board or start from the sprint goal instead.
How do remote teams run a daily standup?
Distributed teams across time zones often run an asynchronous daily standup: each person posts a written update in a shared channel or tool, and the team meets live only when a blocker needs discussion. The same rules apply as in person: keep updates tied to the team's goal and the work on the board, and name blockers precisely.
Related terms
Scrum
An agile framework of short Sprints, three roles and regular inspection.
Extreme Programming (XP)
An agile method built on intensive engineering practices.
Sprint Goal
The single outcome a Scrum team commits to achieving in a sprint.
Information Radiator
A highly visible board or screen showing a team's status at a glance.