Most candidates can name all five Scrum events and recite the Daily Scrum’s 15-minute timebox without hesitation. But the PSM I exam doesn’t reward recitation — it rewards accurate understanding. The Daily Scrum is the event where that gap is most painfully exposed, because two widely-taught ideas about it are simply wrong: that the Scrum Master runs it, and that the three prescribed questions are part of the Scrum framework. Both were never true in the 2020 Scrum Guide, and both will cost you points.
This post walks through exactly what the Scrum Guide says about the Daily Scrum, where candidates go wrong on exam questions, and how to think about this event so that the tricky scenarios become straightforward.
What the Scrum Guide Actually Says
Here is the complete definition from the 2020 Scrum Guide, worth internalizing word for word:
“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.”
That one sentence contains the exam’s two most testable facts about the Daily Scrum: its purpose is tied to the Sprint Goal and its output is an adapted Sprint Backlog. Neither of those is optional — they are the point of the event.
The Scrum Guide then adds:
- It is a 15-minute event — a hard timebox, regardless of Sprint length.
- It is held every working day of the Sprint, at the same time and place to reduce complexity.
- It is for the Developers of the Scrum Team — not the full Scrum Team by default.
- Developers can select whatever structure and techniques they want, as long as the Daily Scrum focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work.
- It is not the only time Developers are allowed to 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.
That last point matters on the exam. Candidates sometimes assume the Daily Scrum is the only coordination mechanism available to the Developers. The Scrum Guide explicitly contradicts that.
The Most Common Wrong Answer: “The Scrum Master Facilitates the Daily Scrum”
This is the misconception that trips up more PSM I candidates than any other aspect of this event.
The Daily Scrum is owned by the Developers. The Scrum Guide assigns it to them, not to the Scrum Master. The Scrum Master’s job, per the Guide, is to ensure that all Scrum events take place and are positive, productive, and kept within the timebox. That means the Scrum Master serves the event — they might help the team keep to 15 minutes, coach them on what good looks like, or work to remove structural obstacles that make the event hard to run. They are not the facilitator-in-charge running the agenda.
Why does this matter on the exam? Because many scenario questions will describe a Daily Scrum that isn’t going well — the team runs long, digresses into problem-solving, or skips it altogether — and then ask what the Scrum Master should do. The correct answer will reflect the Scrum Master as someone who helps the Developers self-manage and improve the event, not someone who steps in and takes it over.
A Scrum Master who runs the Daily Scrum as their meeting has replaced one form of command-and-control with another. The exam consistently penalizes that pattern.
Who Actually Attends the Daily Scrum
The Scrum Guide is specific here, and the specificity matters. The Daily Scrum is an event for the Developers. The Product Owner and Scrum Master are not default participants.
The exception, stated clearly in the Guide: “If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they participate as Developers.”
Read that carefully. The condition is not “if they want to be updated” or “if they have something to add.” It is specifically if they are actively working on Sprint Backlog items. When that’s the case, they participate in the same capacity as anyone else doing Sprint work — as Developers, not in their named accountability.
The exam will sometimes describe a scenario where the Product Owner wants to attend the Daily Scrum to monitor progress, or where the Scrum Master attends every day to listen in. Neither of those is aligned with the Scrum Guide. The Daily Scrum is not a status report to stakeholders or leadership — including the Product Owner.
What About Stakeholders?
The Scrum Guide doesn’t prescribe stakeholder attendance at the Daily Scrum. The event is defined as the Developers’ planning session for the day. The appropriate forum for stakeholder interaction is the Sprint Review, where the team presents their work and collaborates on what comes next. Candidates who conflate the two events struggle with questions about stakeholder engagement.
The Three Questions Are Not Part of Scrum
For many years, Scrum practitioners were taught to structure the Daily Scrum around three questions: What did I do yesterday? What will I do today? What is blocking me? This pattern was useful in practice, and the earlier versions of the Scrum Guide did reference it.
The 2020 Scrum Guide removed it entirely.
The current Guide says: “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.”
The three questions are not prohibited — teams can still use them if they find them useful. But they are not a Scrum rule. The exam is based on the 2020 Scrum Guide, not on habits or training materials from earlier years. If a question asks you to identify correct statements about the Daily Scrum format, any answer that says the three questions are required is wrong.
More importantly, the 2020 version shifted the focus from individual updates to collective progress toward the Sprint Goal. That shift is intentional and testable. A Daily Scrum where each person lists their tasks but nobody connects the discussion to the Sprint Goal is missing the point of the event, even if it runs 15 minutes and everyone attends.
The Purpose: Inspect and Adapt, Every Day
The Daily Scrum is one of Scrum’s five formal events, and like all of them, its purpose is inspection and adaptation. The specific targets here are:
- What to inspect: Progress toward the Sprint Goal
- What to adapt: The Sprint Backlog — specifically the upcoming planned work
This makes the Daily Scrum the mechanism by which the Sprint Backlog stays current. During Sprint Planning, the Developers create a plan. During the Sprint, reality diverges from that plan — always. The Daily Scrum is the structured daily opportunity to close that gap, keeping the plan accurate and the team aligned.
The Scrum Guide reinforces this by explicitly saying the Daily Scrum improves communications, identifies impediments, promotes quick decision-making, and eliminates the need for other meetings. That last phrase is worth pausing on. A functioning Daily Scrum should reduce the total time spent in coordination meetings across the Sprint — not add to it.
When a team skips the Daily Scrum, or runs it as a rote check-in with no real discussion, they lose the daily adaptation mechanism. Problems accumulate quietly until they surface at the Sprint Review, by which point the cost of correction is much higher.
How the Exam Tests This Event
PSM I questions about the Daily Scrum tend to fall into a few consistent patterns. Understanding these patterns helps you recognize what a question is actually testing before you evaluate the answer choices.
Pattern 1: Who is responsible?
A scenario describes a problem with the Daily Scrum — it runs over time, team members show up late, it’s turning into a problem-solving session — and asks what should happen. The correct answer will reflect that the Developers own the event and are responsible for fixing it, often with coaching support from the Scrum Master. Wrong answers will assign the Scrum Master a directive or control role, or suggest adding an external facilitator.
Pattern 2: What is the purpose?
A question will describe a Daily Scrum being used for something other than its stated purpose — for example, to report status to the Product Owner, to plan the next Sprint, or to update a project manager. The correct answer will identify that this use is inconsistent with the Scrum Guide. The Daily Scrum is a planning event for Developers, aimed at the Sprint Goal.
Pattern 3: Attendance and participation
A scenario will include someone other than the Developers in the Daily Scrum — a stakeholder, a Product Owner who isn’t working on Sprint Backlog items, a manager. Questions will test whether you know who the event is for and under what conditions non-Developers participate.
Pattern 4: The timebox and frequency
15 minutes, every working day. The exam occasionally tests whether candidates understand that the timebox doesn’t scale with Sprint length. A two-week Sprint and a four-week Sprint both have 15-minute Daily Scrums. This is different from most other Scrum events, which are timeboxed proportionally to Sprint length.
Pattern 5: What happens after the Daily Scrum?
Some questions ask whether additional discussions are allowed after the Daily Scrum concludes. The Scrum Guide is explicit: the Daily Scrum is not the only time Developers can adjust their plan. They regularly meet throughout the day for more detailed work. The 15-minute event is the structured minimum, not the ceiling on collaboration.
A Scenario Worth Working Through
Here is a representative scenario type you’ll encounter:
The Scrum Master notices that the Developers’ Daily Scrum consistently runs 30 minutes and often turns into a problem-solving session. What should the Scrum Master do?
Common wrong answers: cancel the event, reduce it to three times per week, take over facilitation to enforce the timebox, or extend the timebox since the team clearly needs more time.
The correct approach: coach the Developers on the purpose of the Daily Scrum and help them develop techniques to keep it focused on the Sprint Goal and producing an actionable plan within 15 minutes. Problem-solving can happen in separate discussions after the Daily Scrum, as the Scrum Guide explicitly permits.
The principle underlying the correct answer is self-management. The Scrum Master helps the team improve; they don’t replace the team’s ownership of their own event.
Connecting the Daily Scrum to the Rest of the Framework
The Daily Scrum doesn’t exist in isolation. Understanding how it connects to the other elements of the framework prevents a category of mistakes on scenario questions.
The Sprint Backlog is the plan that the Daily Scrum adapts. It is created during Sprint Planning and updated throughout the Sprint as the Developers learn more. The Daily Scrum is the scheduled moment to make that adaptation explicit, but the Sprint Backlog can and should be updated at any point during the Sprint.
The Sprint Goal is the fixed target against which progress is inspected. The Sprint Goal doesn’t change during the Sprint (making changes that would endanger it is prohibited). The work in the Sprint Backlog can be renegotiated with the Product Owner; the Sprint Goal cannot. This distinction matters in questions that describe a team wanting to change direction mid-Sprint.
The Developers’ accountability to adapt their plan each day toward the Sprint Goal — stated explicitly in the Scrum Guide’s description of the Developers’ responsibilities — maps directly onto what the Daily Scrum enables. It’s not a nice-to-have coordination practice; it’s how Developers fulfill one of their core accountabilities.
What This Means for Your Exam Preparation
If you’ve been studying from older materials, training content that predates 2020, or third-party sources that still reference the three questions as required, you need to reset your understanding against the current Scrum Guide. The exam is based exclusively on the 2020 version.
The questions to ask yourself when reviewing this event:
- Who is the Daily Scrum for? (Developers — not the full Scrum Team by default)
- What is being inspected? (Progress toward the Sprint Goal)
- What is being adapted? (The Sprint Backlog — the upcoming planned work)
- What does the Scrum Master’s role look like here? (Serving and coaching, not directing)
- Is there a prescribed format? (No — Developers choose whatever structure serves the purpose)
- Is the Daily Scrum the only time to adjust the plan? (No — Developers meet throughout the day as needed)
If you can answer all of those from memory and reason through a scenario that applies them, you’re well-positioned on this event.
For PSM I candidates, the Daily Scrum also connects to questions on self-management, impediment removal, and the Scrum Master’s servant leadership. For PSPO I candidates, it comes up in questions about the Product Owner’s relationship to the Developers and what constitutes appropriate oversight versus interference.
The best way to check your Daily Scrum understanding — and every other event — is to work through scenario questions that force you to apply the concepts rather than recall definitions. The PSM I Exam Simulator includes 800+ questions covering Daily Scrum scenarios alongside the full range of PSM I exam topics, with detailed explanations for every answer. If you’re studying for PSPO I, the PSPO I Exam Simulator covers the Product Owner’s relationship to Scrum events in depth. Or grab both with the bundle and cover every angle.
Not ready to commit? Start with the free 20-question PSM I practice test to see where your gaps are right now.