Daily Standup: Format, Questions & Timebox [2026]
A. Togay Koralturk, Best-Selling PMP Author
Last updated on August 23, 2026
11 min read
Few agile rituals are as loved, hated, and misunderstood as the daily standup. Done well, it takes fifteen minutes and leaves a team aligned and unblocked; done badly, it becomes a thirty-minute status parade where everyone reports to a manager and nobody listens. The difference is not the meeting — it is understanding who it is actually for. This guide explains the daily standup in full: what it is, its purpose, the three questions, who attends, how to run one, the anti-patterns that ruin it, and how it appears on the PMP and CAPM exams.
What is a daily standup?
A daily standup is a short, 15-minute meeting an agile team holds every working day of the sprint to synchronize on progress, coordinate the day ahead, and surface anything blocking the work. In Scrum it is called the daily scrum, and the name "standup" comes from the practice of standing up during it — a simple trick to keep it brief.
It is deliberately the smallest of the agile events: no slides, no lengthy discussion, just a quick, focused touchpoint. The team looks at where the work stands relative to the sprint goal, each member gets a moment to flag what they are doing and where they are stuck, and the group leaves knowing how to spend the next day. Crucially, it is a coordination meeting among the people doing the work — not a reporting session run for the benefit of a manager. That single distinction, more than any format or tool, is what separates a standup that helps from one that drains.
The purpose of a daily standup
The purpose of a daily standup is for the team to inspect its progress toward the sprint goal and adapt its plan for the day, surfacing impediments early so they can be cleared. It is an inspect-and-adapt checkpoint, not a status update: the value is in the team re-planning together, not in individuals accounting for their time.
Three things should happen in those fifteen minutes. The team checks progress against the sprint goal, so everyone shares the same picture of how the sprint is tracking. It plans the next day, adjusting who works on what to keep the most important work moving. And it surfaces blockers — the dependencies, questions, and obstacles that, left unspoken, quietly stall a sprint. Notice what is missing: solving those blockers in detail. The standup exists to raise impediments and decide who will handle them; the actual problem-solving happens immediately afterward, among the people involved. Keep that boundary and the meeting stays short and useful; blur it and it sprawls.
Ready to take the next step in project management?
200,000+ Learners Trust Our Instructors
The three daily standup questions
The classic daily standup format has each team member answer three questions. They remain the most common way to run a standup, though — importantly — the 2020 Scrum Guide made them optional rather than a rule.
- What did I do yesterday? What I completed that moves the team toward the sprint goal.
- What will I do today? What I plan to pick up next, so the team can coordinate and spot overlaps.
- What is blocking me? Any impediment, dependency, or question that is slowing me down.
The three questions are a helpful scaffold, especially for newer teams, but they are also where standups most often go wrong: answered mechanically and aimed at the facilitator, they turn into a round of status reports. The 2020 Scrum Guide dropped them as a requirement precisely to free teams to focus on the sprint goal however works best for them. Whatever prompts you use, the test is the same — did the conversation help the team re-plan and unblock, or did it just fill fifteen minutes?
Who attends and who runs it?
The daily standup belongs to the people doing the work. In Scrum, that means the developers own and run it — it is their meeting to coordinate their day. Other roles have a place, but a carefully limited one, and getting this right is what keeps the standup from drifting into a management check-in.
| Role | Part in the daily standup |
|---|---|
| Developers | Own and run the standup. They inspect progress toward the sprint goal, plan the day, and raise blockers. It exists for them. |
| Scrum Master | Ensures the standup happens and stays within 15 minutes, and coaches the team to keep it effective — but does not need to run it or be its audience. |
| Product owner | Attends and participates only when actively working on sprint backlog items; otherwise optional. Does not direct the meeting. |
| Stakeholders / managers | Generally not participants. If present, they observe silently; the standup is not a report delivered to them. |
The most common structural mistake is letting a Scrum Master, product owner, or manager become the person everyone reports to. The moment that happens, the meeting stops being the team's own coordination tool and becomes status theater. A healthy standup is a conversation the developers have with each other.
How long is a daily standup?
A daily standup is timeboxed to 15 minutes, held at the same time and place every working day of the sprint. The consistency matters as much as the length: a fixed slot removes the overhead of scheduling and turns the standup into a dependable habit rather than another meeting to coordinate.
Fifteen minutes is a ceiling, not a quota — many small teams finish faster. The timebox exists to force focus: it is short enough that people stay standing, stay on point, and push detailed discussions out of the meeting. When a standup regularly runs long, it is almost never because fifteen minutes is too little; it is because the team is solving problems, giving detailed status, or letting one topic dominate. The fix is to protect the boundary, not extend the clock. If deeper conversation is needed, that happens right after, with only the people it concerns.
How to run a daily standup meeting
Running a good standup is less about a rigid script than about protecting its focus and its timebox. Most teams use one of two formats, and the mechanics below keep either one tight:
- Pick a format. The two common approaches are round-robin (each person speaks in turn) and walk the board, where the team moves across its task board from the work nearest "done" backward, discussing each item rather than each person. Walk-the-board keeps attention on the work and the sprint goal rather than on individual status.
- Same time, same place, every day. Hold it at a consistent moment, ideally at the start of the working day, so it becomes automatic.
- Keep it to fifteen minutes. Stand up, stay focused, and resist the pull into detail. The Scrum Master or a rotating facilitator gently guards the timebox.
- Raise blockers, don't solve them. When an impediment surfaces, note it and who will help, then move on. Deep dives happen in a follow-up — often called the "after-party" — with just the people involved.
- Update the board. Reflect the real state of the work on the burndown chart or task board as you go, so the team plans from reality, not memory.
The whole thing should feel brisk and slightly energizing, not like a meeting you dread. If people leave knowing what to do next and who to talk to about what is stuck, it worked.
Daily standup vs. daily scrum
Daily standup and daily scrum refer to essentially the same event — a short, daily team sync — with the difference being one of vocabulary and origin. "Daily scrum" is the term from the Scrum framework, where it is a formally defined event; "daily standup" is the more generic, framework-agnostic name used across agile, and even by teams that don't follow Scrum by the book.
In practice, people use the two interchangeably, and that is usually fine. The nuance worth knowing: the daily scrum comes with Scrum's specific expectations — 15 minutes, held by the developers, focused on the sprint goal — whereas a "standup" in a looser agile or scrumban setup may be adapted more freely, for example organized around the flow of work on a Kanban board rather than a sprint goal. The spirit is identical: a brief, regular checkpoint to align and unblock. Only the surrounding rules differ.
Best practices and anti-patterns
Standups fail in predictable ways, and each failure has a matching fix. The table below pairs the most common anti-patterns with what to do about them.
| Anti-pattern | The fix |
|---|---|
| Status theater — everyone reports to the manager or Scrum Master | Redirect the conversation among the developers; the meeting is theirs, not a report to anyone. |
| Running over 15 minutes | Protect the timebox; move any detailed discussion to an after-standup follow-up. |
| Solving problems in the meeting | Raise the blocker, name who will help, and take the deep dive offline. |
| One person dominating | Use walk-the-board or a round-robin so every voice and every work item gets air time. |
| Mechanical three-question recital | Focus on the sprint goal and real coordination, not a rote script aimed at nobody. |
Beyond fixing anti-patterns, a few positive habits make standups genuinely useful: hold it at the same time daily, keep the sprint goal visible, make sure every blocker gets an owner, and end on time even if that means cutting a tangent. A standup is one of the cheapest coordination tools a team has — the discipline is in keeping it that way.
Daily Standup on the PMP® and CAPM® Exams
Because the current PMP exam leans heavily on agile and hybrid ways of working, the daily standup appears as an example of a self-management event and of the project manager acting as a servant leader. The facts to hold onto: it is timeboxed to 15 minutes, held daily, owned by the team doing the work, and focused on progress toward the goal and on removing impediments — not on reporting status upward.
Situational questions tend to describe a standup gone wrong — it has become a status meeting for a manager, it runs long, or the team solves problems in it instead of coordinating — and reward the answer that restores the team's ownership and the event's purpose. The project manager's job is to facilitate and remove blockers, not to run the meeting as a check-in. The CAPM tests the same material more directly, often the timebox, the attendees, or the purpose. Our PMP Complete Study Guide, the most complete on the market, covers the agile events and the servant-leadership mindset the exam expects.
PMP Practice Question: Daily Standup
On an agile team, the daily standup has grown to 30–40 minutes. Each developer delivers a detailed status update aimed at the functional manager, who attends every day and asks follow-up questions; blockers are noted but rarely resolved, and several developers have started tuning out. The Scrum Master wants to fix the event.
What is the best course of action?
a) Ask the functional manager to stop attending, so the standup returns to being an event held among the developers only.
b) Coach the developers to re-center the standup on the sprint goal, each person speaking to the plan for the next 24 hours, with detailed discussion taken offline afterward.
c) Timebox each speaker to two minutes and rotate facilitation among the developers, so the meeting fits back inside its 15-minute box.
d) Replace the standup with a written asynchronous update each morning, so coordination happens without anyone losing meeting time.
Correct answer: B.
Rationale: The event's purpose has inverted: it reports upward instead of planning forward, and every symptom in the stem — the length, the tuned-out developers, the unresolved blockers — flows from that inversion. Coaching the developers to run it as their own inspection of progress toward the sprint goal restores the purpose, and the timebox and the manager's daily interest tend to resolve themselves once the format stops serving them. Choice a) removes the audience but keeps the habit, since status reports with no listener are still status reports, and barring a stakeholder wins a turf battle rather than fixing an event; choice c) is the tempting mechanical fix, but compressing the theater only produces a faster status meeting; choice d) concedes the standup is nothing but reporting and gives up the real-time coordination and daily re-planning that are its actual value. To drill this kind of facilitation judgment, work through our PMP practice exams or, at the entry level, our CAPM practice exams.
Ready to take the next step in project management?
200,000+ Learners Trust Our Instructors
Frequently asked questions
What is a daily standup?
A daily standup is a short, 15-minute meeting an agile team holds every working day of the sprint to sync on progress, plan the day ahead, and surface anything blocking the work. In Scrum it is called the daily scrum. It exists for the team doing the work — to coordinate among themselves — not as a status report to a manager.
What are the three daily standup questions?
The classic format has each member answer: what did I do yesterday, what will I do today, and what is blocking me? These three questions are a common and useful scaffold, but the 2020 Scrum Guide made them optional rather than mandatory, so teams are free to run the standup in whatever way best keeps them focused on the sprint goal.
Who attends and who runs a daily standup?
The developers own and run the daily standup; it is their coordination meeting. The Scrum Master ensures it happens and stays within the timebox but does not need to run it. The product owner participates only when actively working on sprint backlog items. Managers and stakeholders are generally not participants and should not be the audience.
How long should a daily standup be?
A daily standup is timeboxed to 15 minutes and held at the same time and place every working day of the sprint. Fifteen minutes is a maximum, not a target, and many teams finish faster. If it regularly runs long, the cause is usually detailed problem-solving or status-reporting creeping in — the fix is to take those offline, not to extend the meeting.
What is the difference between a daily standup and a daily scrum?
They refer to essentially the same event. "Daily scrum" is the term from the Scrum framework, where it is a formally defined 15-minute event owned by the developers and focused on the sprint goal. "Daily standup" is the more generic agile term used across frameworks. People use them interchangeably; the daily scrum simply carries Scrum's specific expectations.
Does the product owner attend the daily standup?
The product owner attends and participates in the daily standup only when they are actively working on sprint backlog items, in which case they take part as a team member. Otherwise their attendance is optional, and even when present they do not direct the meeting — the daily standup is the developers' event to coordinate their own work.
Is the daily standup on the PMP exam?
Yes. The current PMP exam covers agile and hybrid approaches heavily, and the daily standup appears as an example of team self-management and servant leadership. You are expected to know it is a 15-minute, team-owned, daily event for inspecting progress and removing blockers, and to recognize when it has degraded into a top-down status meeting.
Is the daily standup on the CAPM exam?
Yes. The CAPM covers the Scrum events, including the daily scrum, usually a little more directly than the PMP — often testing the timebox, who attends, or its purpose. Because the CAPM is scenario-based, you should also be ready to spot a standup being run incorrectly, such as one turned into a status report for a manager.
What Is Scrum? Roles, Events & Artifacts [2026]
Scrum is a lightweight agile framework for complex work. Its theory, the 3 roles, 5 events, and 3 artifacts, scrum vs. agile, benefits, and PMP exam tips.
Scrum Master: Role, Responsibilities & Skills [2026]
A scrum master is a servant leader who helps a team work effectively. Responsibilities, scrum master vs. project manager, skills, becoming one, and exam tips.
Product Owner: Role, Responsibilities & Skills [2026]
The product owner maximizes a product's value and owns the backlog. Responsibilities, product owner vs. scrum master, skills, how to become one, and exam tips.
