4.3 Daily Scrum
Key Takeaways
- The Daily Scrum’s purpose is to inspect progress toward the Sprint Goal, adapt the Sprint Backlog, and produce an actionable plan for the next day of work
- It is a 15-minute event for the Developers, held at the same time and place every working day of the Sprint to reduce complexity
- The Product Owner and Scrum Master participate as Developers only if they are actively working on Sprint Backlog items
- Developers choose the structure and techniques; the meeting must stay focused on the Sprint Goal and next-day plan
- The Product Owner is not required to attend; the Daily Scrum is not a status report to the PO or management
4.3 Daily Scrum
Scrum Guide 2020: The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work.
For PSPO I, Daily Scrum questions often target attendance myths and status-report anti-patterns. If you remember only one sentence, remember this: it is a 15-minute event for the Developers to improve the plan toward the Sprint Goal—not a mandatory daily briefing for the Product Owner.
Purpose Before Format
The Daily Scrum exists to:
- Inspect progress toward the Sprint Goal.
- Adapt the Sprint Backlog as necessary.
- Produce an actionable plan for the next day of work.
Those outcomes create focus and improve self-management. Secondary effects the Guide names include improved communications, identification of impediments, quicker decision-making, and reduced need for other meetings. None of those effects justify turning the event into a lengthy design workshop, a defect triage with every stakeholder, or a management dashboard readout.
If the conversation does not improve tomorrow’s plan relative to the Sprint Goal, it is not serving the Daily Scrum’s purpose—regardless of whether people answered three ritual questions.
Who the Event Is For
The Daily Scrum is a 15-minute event for the Developers of the Scrum Team. To reduce complexity, it is held at the same time and place every working day of the Sprint.
Product Owner and Scrum Master attendance
If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they participate as Developers. That clause is precise:
- Active contribution to Sprint Backlog work → they join in the Developer role for that work.
- Not actively working Sprint Backlog items → they are not required attendees of the Daily Scrum.
Critical exam trap: The Product Owner is NOT required to attend the Daily Scrum. Many organizations train POs to “always show up for standup.” That may be a local habit; it is not a Scrum Guide rule. The PO’s daily availability for clarification is still valuable, but it is not the same as mandatory Daily Scrum membership.
Likewise, the Scrum Master is accountable for the Scrum Team’s effectiveness and for establishing Scrum as described in the Guide. That does not mean the SM must run every Daily Scrum as a facilitator with a script, nor that the SM turns the event into a personal status collection. If the SM is not doing Sprint Backlog item work, mandatory daily attendance as a status recipient is not what the Guide describes.
Stakeholders and managers
The Daily Scrum is not designed as an open stakeholder forum. Turning it into a parade of executives collecting individual status undermines self-management and often expands beyond fifteen minutes. Impediments that need organizational help can be surfaced and then handled outside the timebox with the right people—including the Product Owner when value trade-offs are required.
Structure Is the Developers’ Choice
The Developers can select whatever structure and techniques they want, as long as their Daily Scrum:
- Focuses on progress toward the Sprint Goal, and
- Produces an actionable plan for the next day of work.
There is no mandated three-question script in the 2020 Scrum Guide. Older training materials popularized “What did I do yesterday / What will I do today / What impediments do I have?” That pattern can still work if it serves the Goal and next-day plan, but it is not required, and reciting it while ignoring the Sprint Goal fails the purpose test.
Other valid structures might walk the Sprint Backlog board from Goal-critical items, focus on risks to Done, or replan after a discovery—again, Developers choose, Goal and plan remain the constraints.
What Daily Scrum Is Not
Reject these characterizations on the exam and in practice:
| Anti-pattern | Why it fails |
|---|---|
| Status report to the Product Owner | PO is not the audience; Developers inspect and adapt their plan |
| Status report to management | Same problem; empiricism is for the team’s plan, not theater |
| Problem-solving deep dive that routinely blows the timebox | Detailed work happens as needed outside the 15 minutes |
| PO assigning tasks for the day | Developers own how work is planned and adapted |
| Skipping the event because “we talk all day anyway” | Cadence and shared inspection of Goal progress still matter |
| Expanding to full-team design with every stakeholder daily | Purpose and 15-minute timebox are lost |
The Guide notes the Daily Scrum is not the only time Developers may adjust their plan. They often meet throughout the day for more detailed discussions about adapting or re-planning the rest of the Sprint’s work. The Daily Scrum is the lightweight daily checkpoint, not the only collaboration moment.
How the Daily Scrum Connects to PO Accountability
Even when you do not attend, Daily Scrum outcomes affect product value:
- Sprint Goal focus keeps the Increment coherent. If Developers detect the Goal is at risk, they need a path to renegotiate scope with you—not a silent hope that velocity will magically recover.
- Sprint Backlog adaptation may clarify or re-slice work. You remain the partner for scope renegotiation that affects value ordering, while Developers retain how-planning.
- Impediments that are really product decisions (priority conflicts, external dependency trade-offs, unclear acceptance expectations) often require the Product Owner quickly—just not necessarily inside the 15-minute event.
- Quality and Done stay non-negotiable. A Daily Scrum that “plans” to skip Done to look on track is adapting the wrong variable.
Healthy PO pattern: be reachable, inspect progress through transparent Sprint Backlog and working product, attend when you are doing Sprint Backlog work or when the team invites advice, and never turn Daily Scrum into your personal control room.
Cadence, Place, and the 15-Minute Timebox
Same time and place every working day reduces coordination cost—people do not renegotiate logistics daily. Remote teams still benefit from a stable slot and channel.
Fifteen minutes is a hard timebox character in spirit: the event is deliberately short so it stays about near-term plan adaptation. If deeper design, pairing, or stakeholder demos are needed, schedule them as separate collaboration—not as “Daily Scrum overtime.”
When Sprints are short (for example one week), Daily Scrums still occur each working day; the container is smaller, but the daily inspect-and-adapt heartbeat remains.
Relationship to Other Events
- Sprint Planning creates the initial Sprint Backlog and Sprint Goal; Daily Scrum adapts that plan daily.
- Sprint Review is the stakeholder-facing inspection of the Increment and Product Backlog—not a substitute for Daily Scrum, and Daily Scrum is not a mini Review.
- Sprint Retrospective improves effectiveness and process; Daily Scrum does not replace the Retro with daily process debates that starve Goal planning.
- The Sprint rules still apply: Daily adaptations must not endanger the Sprint Goal or decrease quality; scope clarification still involves the Product Owner when renegotiation is needed.
PSPO Scenario Drill
Scenario: A Product Owner insists on attending every Daily Scrum to hear each Developer’s status and to reassign tasks when progress looks slow. Stakeholders are invited “so everyone stays aligned.” Meetings regularly run forty minutes. Developers stop discussing real risks because the session became a performance.
Sound approach: Restore purpose and constraints. Daily Scrum is 15 minutes for Developers to inspect Sprint Goal progress and plan the next day; structure is theirs. The PO is not required to attend and does not reassign tasks. If the PO is not actively working Sprint Backlog items, mandatory attendance as status recipient is an anti-pattern. Stakeholder alignment belongs in Sprint Review and other collaboration, not a bloated daily status. The PO stays available for scope and value decisions—often right after Developers identify a need—without converting Daily Scrum into a management meeting.
If you can correct that scenario on sight, you have the Daily Scrum rules PSPO I repeatedly probes: purpose, participants, timebox, optional PO attendance, and Developer ownership of structure and plan.
What is the primary purpose of the Daily Scrum according to the Scrum Guide 2020?
Who is required to attend the Daily Scrum?
Developers want to change how they run the Daily Scrum. Which constraint does the Scrum Guide impose?