4.3 The Daily Scrum

Purpose of the Daily Scrum

The Daily Scrum is a 15-minute event for the Developers of the Scrum Team. Its purpose is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work to produce an actionable plan for the next day of work. The Sprint Goal — not a task board, not individual to-do lists — is the lens through which progress is judged.

To reduce complexity, the Daily Scrum is held at the same time and place every working day of the Sprint. This consistency removes scheduling overhead and lowers cognitive load, so the Developers can spend their fifteen minutes on the work rather than on logistics.

The 15-minute timebox is fixed and does not scale with Sprint length. Whether the Sprint is one week or four weeks, the Daily Scrum is fifteen minutes. This contrasts with Sprint Planning, the Review, and the Retrospective, which all shorten for shorter Sprints. A question proposing a "7-minute Daily Scrum for a one-week Sprint" is testing exactly this trap.

Who Attends and Who Runs It

The Daily Scrum is for the Developers. The 2020 Scrum Guide removed the prescribed three questions ("What did I do yesterday? What will I do today? Any impediments?"). The Developers may now 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. Insisting on the old three-question script is no longer a Scrum requirement — and the exam tests this directly.

• If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they participate as Developers — not as observers collecting updates.
• The Scrum Master ensures the Daily Scrum takes place, but the Developers are responsible for conducting it. The Scrum Master coaches the team toward keeping it within fifteen minutes; they do not chair it.
• It is not a status meeting reported up to the Scrum Master, a project manager, or stakeholders. This is one of the most frequently tested distinctions on PSM I.

Not the Only Time to Adapt

A common misconception is that Developers may only change their plan during the Daily Scrum. The Scrum Guide is explicit: Developers often meet throughout the day for more detailed discussions about adapting or re-planning the rest of the Sprint's work. The Daily Scrum improves communications, identifies impediments, promotes quick decision-making, and consequently eliminates the need for other meetings — but it does not replace ad hoc collaboration. So when a scenario describes Developers huddling at 2 p.m. to rework a tricky integration, that is normal and healthy, not a process violation.

Why This Matters on the Exam

PSM I questions repeatedly probe four ideas about the Daily Scrum:

1. It is for the Developers — not a stakeholder or management update.
2. It is a fixed 15 minutes — longer is a smell, and the timebox never scales with Sprint length.
3. The Sprint Goal is the object of inspection — not a status tour around the room.
4. It is not the only opportunity to re-plan — Developers adapt continuously.

If you anchor on "inspect-and-adapt toward the Sprint Goal, run by the Developers, fifteen minutes," you will answer the large majority of Daily Scrum items correctly. Watch for distractors that hand control to the Scrum Master or Product Owner, that demand the legacy three questions, or that treat the meeting as a reporting ritual.

Worked Scenario: A Developer Misses the Daily Scrum

Suppose a Developer cannot attend a particular Daily Scrum. Does the event still happen? Yes — the Daily Scrum is held every working day regardless of who is present, and a single absence does not cancel it; the remaining Developers still inspect progress toward the Sprint Goal and plan the next day. Should the Scrum Master "discipline" the absent Developer or report the absence to a manager? No — the Scrum Master coaches the team toward valuing the event, but the Daily Scrum is not an attendance-policing mechanism and is never a report to management.

Contrast this with a scenario where the manager wants a daily status read-out: the correct response is that the Daily Scrum is for the Developers and is not a status meeting; the manager can get product progress from the Sprint Review, where stakeholders belong.

How the Scrum Master Helps Without Taking Over

The Scrum Master's relationship to the Daily Scrum is a subtle, frequently tested point. The Scrum Master is a true leader who serves the team. They ensure the event occurs and coach the Developers to keep it within the 15-minute timebox, but they do not facilitate it as a chairperson, assign turns, or collect updates. If the Daily Scrum routinely runs long or drifts into problem-solving that should happen afterward, the Scrum Master coaches the team to recognize and fix that pattern — teaching, not controlling.

Over time the goal is a team that runs its own Daily Scrum effectively without the Scrum Master needing to be present at all. An answer that says "the Scrum Master must attend and run every Daily Scrum" misreads the accountability.