What is the timebox of the Daily Scrum?

15 minutes, held every working day of the Sprint.

Who is required to attend the Daily Scrum?

Developers. The event is for Developers of the Scrum Team.

Primary purpose of the Daily Scrum?

To inspect progress toward the Sprint Goal and adapt the Sprint Backlog, adjusting the plan for the next 24 hours.

Who owns and can change the Sprint Backlog during the Sprint?

Developers. They own the Sprint Backlog and adapt it as they learn.

What must discussions in the Daily Scrum focus on?

Progress toward the Sprint Goal and the plan to achieve it, not individual status reporting.

Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.

Sprints are the heartbeat of Scrum, where ideas are turned into value.

An Increment is a concrete stepping stone toward the Product Goal.

Daily Scrum: Inspect-and-Adapt Engine for Developers — Professional Scrum Master I (PSM I) Complete Exam-Ready Mastery Course

Daily Scrum in the Big Picture of Scrum

Where the Daily Scrum Fits

Inside each Sprint, the Scrum Team uses events to apply empiricism. The Daily Scrum is the Developers' main inspect-and-adapt engine during the Sprint.

Key Roles Refresher

The Scrum Team is a cohesive unit focused on one Product Goal. Within it: the Product Owner maximizes value, the Scrum Master establishes Scrum, and Developers create aspects of a usable Increment.

Sprint Backlog Ownership

The Sprint Backlog holds the Sprint Goal (why), selected Product Backlog items (what), and an actionable plan (how). The Daily Scrum belongs to Developers and supports their ownership of this plan.

What You Will Learn

You will learn the purpose, timebox, and attendees of the Daily Scrum, how it embodies empiricism, how it drives Sprint Backlog adaptation, and which exam-trap anti-patterns to avoid.

Definition, Purpose, and Timebox of the Daily Scrum

Core Definition

The Daily Scrum is a 15-minute event for the Developers of the Scrum Team. It happens every working day of the Sprint at a time and place they choose.

Purpose in One Sentence

Its purpose is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming work.

Empiricism in Action

Daily Scrum supports transparency (shared state), inspection (of progress), and adaptation (plan for next 24 hours) in a tight feedback loop.

Who Must Attend

Only Developers are required. Scrum Master and Product Owner may join, but the event is for Developers. Timebox is strictly 15 minutes.

Developers’ Ownership and the Link to the Sprint Backlog

Developers and the Plan

Developers are committed to creating aspects of a usable Increment. The Sprint Backlog is their plan: Sprint Goal (why), selected items (what), and actionable plan (how).

Key Question Each Day

At the Daily Scrum, Developers ask: "Given what we now know, is our plan still the best way to achieve the Sprint Goal?" If not, they change the plan.

Typical Adaptations

They may re-order tasks, swarm on critical work, split items into smaller pieces, or drop tasks that do not help the Sprint Goal.

Exam Nuance

Only Developers change the Sprint Backlog. The Product Owner can suggest, but cannot force. Changes are expected as long as the Sprint Goal remains intact.

A Walkthrough: 15-Minute Daily Scrum in Practice

Setting the Scene

A team is building a "Team Chat" feature. Sprint Goal: "Enable users to send and receive real-time messages in 1:1 chats." It is day 5 of a 2-week Sprint.

Start with the Sprint Goal

Developers begin: "Let’s check where we are against our Sprint Goal." This orients discussion around outcomes, not personal status.

Inspect Work and Quality

Backend persistence is Done per the Definition of Done. Websockets are flaky under load. Chat UI is only half-done and took more effort than expected.

Adapt the Plan

Developers swarm on websocket stability, split the UI item into basic and polish, and postpone a low-impact logging task that does not affect the Sprint Goal.

From Old 3 Questions to Modern Daily Scrum

The Old 3 Questions

Historically, many teams used three questions: yesterday, today, impediments. These are now optional, not prescribed by the Scrum Guide.

Current Guidance (2020+)

Developers choose the structure. The only requirement is that the Daily Scrum inspects progress toward the Sprint Goal and adapts the plan for the next 24 hours.

Exam Trap

If an answer says Developers must answer the three questions or the Scrum Master asks them, it conflicts with the current Scrum Guide and is likely wrong.

Modern Patterns

Teams might walk the board, focus on Sprint Goal-related work, and discuss coordination and risks instead of reciting individual status.

Common Anti-Patterns and Exam Traps

Status Meeting Smell

Anti-pattern: Developers report one by one to a manager, Product Owner, or Scrum Master. Correct: Developers talk to each other about the work and Sprint Goal.

Scrum Master Interrogation

Anti-pattern: Scrum Master asks each person the three questions and judges answers. This undermines self-management and Developers' ownership.

Overlong Problem-Solving

Anti-pattern: deep technical debates inside the 15 minutes. Correct: surface issues, then schedule follow-up with the right people.

Skipping or Crowding the Event

Anti-patterns: skipping the Daily Scrum or allowing external observers to dominate. Both damage transparency and focus on the Sprint Goal.

Thought Exercise: Rewrite a Bad Daily Scrum

Use this exercise to practice spotting and fixing Daily Scrum anti-patterns.

Scenario:

A team does the following every morning:

The Scrum Master stands at the front and calls on each Developer by name.
Each Developer answers: "Yesterday I did X, today I will do Y, no impediments."
The Product Owner asks several questions about dates and delivery commitments.
The meeting often runs 30 minutes.
No one mentions the Sprint Goal. The Sprint Backlog is not updated.

Your tasks (mentally or in notes):

List at least three anti-patterns you see.
For each anti-pattern, write a Scrum-consistent alternative behavior.
Rewrite the flow of the meeting in 5 bullet points that describe a good Daily Scrum.

Hints to check yourself:

Who should own and run the event?
What is the timebox?
What should the focus be (and not be)?
What should happen to the Sprint Backlog afterwards?

After you write your version, compare it mentally with this checklist: Developers lead, 15 minutes, Sprint Goal-centric, plan for next 24 hours, follow-up discussions scheduled outside the timebox, Sprint Backlog updated as needed.

Quiz 1: Purpose and Attendees of the Daily Scrum

Test your understanding of who the Daily Scrum is for and why it exists.

Which statement best describes the Daily Scrum according to the current Scrum Guide?

A 15-minute status meeting where Developers report progress to the Scrum Master and Product Owner.
A 15-minute event where Developers inspect progress toward the Sprint Goal and adapt their plan for the next 24 hours.
A daily planning meeting led by the Product Owner to reprioritize the Product Backlog.
An optional meeting for any interested stakeholders to ask questions about the product.

Show Answer

Answer: B) A 15-minute event where Developers inspect progress toward the Sprint Goal and adapt their plan for the next 24 hours.

The Daily Scrum is a 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog (their plan) for the next 24 hours. It is not a status report to the Scrum Master or Product Owner, nor is it for reprioritizing the Product Backlog or general stakeholder Q&A.

Quiz 2: Identifying Anti-Patterns

Check your ability to spot Daily Scrum anti-patterns that often appear in exam options.

During a Daily Scrum, the Scrum Master asks each Developer the three questions, one by one, and then decides who should work on which task. What is the best Scrum-consistent response?

This is correct, because the Scrum Master is accountable for the efficiency of the Scrum Team.
This is acceptable only if the meeting finishes within the 15-minute timebox.
This is not correct, because Developers should self-manage and choose how to structure the Daily Scrum.
This is required, because the Scrum Guide prescribes the three questions for the Daily Scrum.

Show Answer

Answer: C) This is not correct, because Developers should self-manage and choose how to structure the Daily Scrum.

Developers are self-managing and own the Sprint Backlog. They decide how to run the Daily Scrum. The Scrum Guide no longer prescribes the three questions, and the Scrum Master should not assign tasks. Timebox alone does not make this behavior correct.

Flashcards: Key Daily Scrum Facts

Use these cards to lock in core Daily Scrum details that PSM I questions frequently target.

What is the timebox of the Daily Scrum?: 15 minutes, held every working day of the Sprint.
Who is required to attend the Daily Scrum?: Developers. The event is for Developers of the Scrum Team.
Primary purpose of the Daily Scrum?: To inspect progress toward the Sprint Goal and adapt the Sprint Backlog, adjusting the plan for the next 24 hours.
Who owns and can change the Sprint Backlog during the Sprint?: Developers. They own the Sprint Backlog and adapt it as they learn.
What must discussions in the Daily Scrum focus on?: Progress toward the Sprint Goal and the plan to achieve it, not individual status reporting.
Is the three-question format mandatory in the Daily Scrum?: No. Developers choose the structure as long as they inspect and adapt toward the Sprint Goal.
What happens if deep problem-solving arises during the Daily Scrum?: Note the issue, keep the Daily Scrum within 15 minutes, and schedule follow-up discussions with relevant people.

Connecting Daily Scrum Insights to Sprint Backlog Changes

Scenario Setup

Sprint Goal: "Allow customers to reset their password via email." API integration and a security review turn out more complex than expected.

Inspecting During Daily Scrum

Developers see the API risk threatens the Sprint Goal and that a low-priority analytics task is not essential for achieving it.

Adapting the Sprint Backlog

They split the email integration item, focus on basic send plus security review, and move or drop analytics work that does not affect the Sprint Goal.

Exam Perspective

Scrum-consistent options show Developers updating the Sprint Backlog based on Daily Scrum insights, without needing external permission to adjust their plan.

Putting It All Together and Next Steps in Your Study Path

Daily Scrum in One Line

A 15-minute daily event for Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog for the next 24 hours.

Ownership and Empiricism

Developers own both the Daily Scrum and the Sprint Backlog. The event drives transparency, inspection, and adaptation inside the Sprint.

Avoiding Anti-Patterns

Watch for status reporting, Scrum Master interrogations, long problem-solving, skipped events, or outsider domination in exam scenarios.

Your Study Path

Next, use Skarp diagnostics, mock exams, spaced review, and gap guides to reinforce these concepts and connect them to other Scrum events.

Key Terms

Scrum: Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.
Sprint: Sprints are the heartbeat of Scrum, where ideas are turned into value.
Increment: An Increment is a concrete stepping stone toward the Product Goal.
Developers: Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.
Scrum Team: The Scrum Team is a cohesive unit of professionals focused on one objective at a time, the Product Goal.
empiricism: Scrum is founded on empiricism and lean thinking.
Daily Scrum: A 15-minute event for the Developers of the Scrum Team to inspect progress toward the Sprint Goal and adapt the Sprint Backlog, adjusting the plan for the next 24 hours.
Sprint Goal: The Sprint Goal is the single objective for the Sprint.
Product Goal: The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against.
Scrum Master: The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide.
Product Owner: The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.
Sprint Backlog: The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).
Product Backlog: The Product Backlog is an emergent, ordered list of what is needed to improve the product.
Definition of Done: The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.