3.3 Daily Scrum Event & 15-Minute Timebox

3.3 Daily Scrum Event & 15-Minute Timebox

The Daily Scrum is a 15-minute timeboxed event held every working day for the Developers of the Scrum Team. To minimize operational friction and complexity, the event is held at the same time and place every day of the Sprint.

---

Purpose: Inspection and Adaptation Toward the Sprint Goal

The primary purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, producing an updated, actionable plan for the next 24 hours of work. It is an internal operational alignment meeting designed to increase the likelihood that the team will achieve their Sprint Goal.

+-----------------------------------------------------------------------------------+
|                                 DAILY SCRUM EVENT                                 |
|                                                                                   |
|  TIMEBOX: 15 minutes (do not extend)                                                      |
|  FREQUENCY: Every working day, same time & place                                  |
|  PARTICIPANTS: Mandatory for Developers                                           |
|                                                                                   |
|  CORE OBJECTIVE:                                                                  |
|  1. Inspect progress toward the SPRINT GOAL.                                      |
|  2. Identify impediments blocking completion of work.                             |
|  3. Adapt the Sprint Backlog (create 24-hour execution plan).                     |
+-----------------------------------------------------------------------------------+

---

Who Attends the Daily Scrum?

Understanding attendee roles and boundaries is critical for the PSM I exam:

1. The Developers: Attendance is mandatory for Developers. They own the event, facilitate its execution, and use it to coordinate their work.
2. The Product Owner & Scrum Master:
   • If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog as Developers, they participate as Developers.
   • If they are not working on Sprint Backlog items, they may attend as passive observers. They do not run the meeting, ask for individual updates, or interrupt the Developers.
3. Management & External Stakeholders: External managers or stakeholders should generally not participate in the Daily Scrum to prevent it from turning into a status reporting session.

---

Format and Technique: Developers Decide

A major change introduced in the Scrum Guide 2020 is that the three traditional questions ("What did I do yesterday? What will I do today? What impediments do I have?") are no longer mandatory.

The Developers can select whatever structure, technique, or format they choose, as long as the event focuses strictly on progress toward the Sprint Goal and produces an actionable plan for the next working day. Common modern techniques include:

• Walking the Board: Reviewing Sprint Backlog items from right (closest to Done) to left (newly started) to focus on finishing work before starting new work.
• Focusing on Impediments: Opening the session directly with current impediments or risks threatening the Sprint Goal.
• Sub-group Alignment: Grouping discussion around cluster items supporting specific technical components of the Sprint Goal.

---

Anti-Pattern: The Status Report Trap

The most prevalent real-world and exam anti-pattern is treating the Daily Scrum as a status report delivered to the Scrum Master, Product Owner, or a project manager.

---

The '16th Minute': Handling In-Depth Discussions

The Daily Scrum is limited to 15 minutes. It is not a working session to solve complex architectural problems, debate technical implementations, or negotiate contract terms.

When a complex blocker or technical dispute arises during the Daily Scrum, the Developers note the issue, complete the 15-minute event, and then meet immediately after the Daily Scrum (often referred to as the '16th minute') to discuss detailed solutions. Only the team members required for that specific problem need to stay for the follow-up meeting.

---

Role of the Scrum Master

The Scrum Master's responsibilities regarding the Daily Scrum are limited and specific:

• Ensures that the Developers hold the Daily Scrum.
• Teaches the Developers to keep the Daily Scrum within the 15-minute timebox.
• Ensures that the event remains focused on progress toward the Sprint Goal and does not devolve into a status report.
• The Scrum Master does NOT need to be present at every Daily Scrum. The Developers are self-managing and hold the meeting independently.

---

PSM I Exam Traps & Empirical Guidance

Exam Trap 1: "The Scrum Master is sick and absent from work today. What should happen to the Daily Scrum?"

Scrum Truth: The Developers hold the Daily Scrum as scheduled. The event belongs to the Developers; the Scrum Master's presence is not required for the meeting to occur.

Exam Trap 2: "During the Daily Scrum, two Developers begin a 20-minute debate over a database schema change. What should occur?"

Scrum Truth: The debate must be postponed until after the Daily Scrum concludes. The 15-minute timebox must be preserved for high-level inspection and plan adaptation.

Exam Trap 3: "The Product Owner uses the Daily Scrum to assign new urgent tasks to Developers."

Scrum Truth: The Product Owner cannot assign tasks or introduce scope changes that endanger the Sprint Goal during the Daily Scrum.