Daily Scrum and Adapting the Sprint Backlog: A Comprehensive Guide for PSM II
Introduction
The Daily Scrum is one of the most frequently misunderstood events in the Scrum framework, and understanding how it connects to adapting the Sprint Backlog is critical for passing the PSM II exam. At the Professional Scrum Master II level, you are expected to go far beyond surface-level knowledge. You must demonstrate a deep understanding of the purpose behind the Daily Scrum, the dynamics of Sprint Backlog adaptation, and how a Scrum Master facilitates these practices in complex, real-world scenarios.
Why Is This Topic Important?
The Daily Scrum and the adaptation of the Sprint Backlog sit at the very heart of empiricism in Scrum. Together, they represent the inspection and adaptation loop that occurs daily within a Sprint. Without effective Daily Scrums, the Developers lose their ability to self-manage, detect impediments early, and course-correct toward the Sprint Goal. Without meaningful adaptation of the Sprint Backlog, the team becomes rigid and unable to respond to emerging insights.
For the PSM II exam, this topic is important because:
- It tests your understanding of self-management and how Developers organize their own work.
- It evaluates whether you understand the Daily Scrum as a planning event, not a status meeting.
- It assesses your ability to coach teams away from anti-patterns and toward effective empirical practices.
- It challenges you to differentiate between what the Scrum Guide prescribes and common but incorrect practices.
What Is the Daily Scrum?
According to the Scrum Guide, 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.
Key characteristics of the Daily Scrum include:
- Time-box: 15 minutes maximum.
- Participants: The Developers. The Scrum Master and Product Owner may attend but only if they are actively working on Sprint Backlog items. They do not direct or control the event.
- Frequency: Every working day of the Sprint.
- Same time, same place: Held at the same time and place to reduce complexity. However, this is a guideline for simplicity, not a rigid rule.
- Format: The Developers can choose whatever structure and techniques they want, as long as the focus remains on progress toward the Sprint Goal. The three-question format (What did I do? What will I do? Any impediments?) is not prescribed by the Scrum Guide — it is merely one possible technique.
What Is NOT the Daily Scrum?
Understanding what the Daily Scrum is not is equally important for the PSM II:
- It is not a status meeting where Developers report to the Scrum Master or anyone else.
- It is not the only time Developers can adjust their plan. Developers can and should communicate and re-plan throughout the day as needed.
- It is not a problem-solving session. Detailed discussions and problem-solving should happen outside the Daily Scrum, often immediately after it concludes.
- It is not run by the Scrum Master. The Developers own this event. The Scrum Master ensures they have it and teaches them to keep it within the time-box, but does not facilitate or lead the discussion.
What Is Adapting the Sprint Backlog?
The Sprint Backlog consists of three elements: the Sprint Goal (the why), the set of Product Backlog items selected for the Sprint (the what), and the actionable plan for delivering the Increment (the how). The Sprint Goal is fixed once Sprint Planning concludes, but the what and how are expected to evolve throughout the Sprint.
Adapting the Sprint Backlog means:
- Adding or removing tasks: As Developers learn more about the work, they may decompose items further, create new tasks, or remove tasks that are no longer relevant.
- Re-ordering work: Developers may reprioritize which items they tackle next based on what they learn during the Sprint.
- Negotiating scope with the Product Owner: If Developers discover that they have more or less capacity than expected, they can negotiate with the Product Owner to add or remove Product Backlog items from the Sprint — without changing the Sprint Goal.
- Adjusting the plan: The plan for how to achieve the Sprint Goal is a living artifact that is updated as new information emerges.
The Daily Scrum is the primary formal opportunity for this inspection and adaptation, but it is not the only time it can happen.
How Does the Daily Scrum Work in Practice?
In a well-functioning Scrum Team, the Daily Scrum typically unfolds as follows:
1. Developers gather at the agreed-upon time and place.
2. They inspect progress toward the Sprint Goal. This might involve looking at a Sprint Burndown chart, a task board, or simply discussing where things stand.
3. They identify any obstacles that are impeding progress and determine how to address them.
4. They adapt their plan for the next 24 hours. This is where the Sprint Backlog gets updated — work items are re-assigned, tasks are created or refined, and the approach is adjusted.
5. They produce an actionable plan for the upcoming day of work that optimizes collaboration and moves them closer to the Sprint Goal.
The key outcome of the Daily Scrum is not a report — it is a plan. The Developers leave with a shared understanding of what they will focus on next and how they will work together.
The Role of the Scrum Master
At the PSM II level, you must understand the Scrum Master's nuanced role in relation to the Daily Scrum:
- Teaching and coaching: The Scrum Master helps Developers understand the purpose of the Daily Scrum and how to make it effective. This includes coaching them away from anti-patterns like turning it into a status report.
- Ensuring it happens: The Scrum Master is accountable for ensuring the Daily Scrum takes place, but the Developers are responsible for conducting it.
- Protecting the time-box: If Developers consistently exceed 15 minutes, the Scrum Master coaches them on how to be more focused.
- Removing impediments: When impediments are identified during the Daily Scrum, the Scrum Master may take ownership of removing organizational impediments, while Developers handle technical ones.
- Not facilitating: A common anti-pattern is the Scrum Master acting as a facilitator who calls on each person to speak. This undermines self-management. The Scrum Master should coach the team to run the event themselves.
Common Anti-Patterns and How to Address Them
PSM II questions often present scenarios with anti-patterns. Here are the most common ones:
Anti-Pattern 1: Status Reporting
Developers address the Scrum Master or a manager rather than each other. The conversation feels like individual reports rather than collaborative planning.
Solution: Coach Developers to talk to each other, focus on the Sprint Goal, and think of the Daily Scrum as a planning session.
Anti-Pattern 2: Rigid Three-Question Format
Teams mechanically go around the room answering three questions without meaningful discussion or adaptation.
Solution: Encourage Developers to experiment with different formats — walking the board, focusing on the Sprint Goal, or discussing blockers first. The format should serve the purpose, not replace it.
Anti-Pattern 3: Problem-Solving During the Daily Scrum
Detailed technical discussions derail the event, causing it to exceed 15 minutes.
Solution: Coach Developers to note topics that need deeper discussion and schedule them immediately after the Daily Scrum with only the relevant people.
Anti-Pattern 4: Skipping the Daily Scrum
Teams believe the Daily Scrum is unnecessary because they sit together or communicate frequently.
Solution: Explain that the Daily Scrum provides a formal opportunity for inspection and adaptation. Without it, teams may drift without realizing they are off track. It also creates a shared understanding and alignment that casual conversations may not achieve.
Anti-Pattern 5: The Sprint Backlog Never Changes
The plan created during Sprint Planning is treated as fixed, and no adaptation occurs during the Sprint.
Solution: Coach the team on the living nature of the Sprint Backlog. Help them understand that the Sprint Goal is the commitment, not the specific set of tasks. Adaptation is expected and necessary.
The Connection Between the Daily Scrum and the Sprint Goal
The Sprint Goal is the single objective for the Sprint, and it is the anchor for the Daily Scrum. Every conversation during the Daily Scrum should relate back to the Sprint Goal. Questions like:
- Are we still on track to achieve the Sprint Goal?
- What is the most important thing we can do today to move toward the Sprint Goal?
- Is there anything threatening our ability to meet the Sprint Goal?
These questions keep the Daily Scrum focused and purposeful. If Developers are discussing work that does not relate to the Sprint Goal, it may indicate a problem with Sprint Planning or a lack of understanding of the Sprint Goal's importance.
Adapting the Sprint Backlog Beyond the Daily Scrum
While the Daily Scrum is a key moment for adaptation, it is important to remember that Developers often meet throughout the day to discuss details, adapt, and re-plan. The Daily Scrum does not replace ongoing collaboration — it complements it by providing a regular rhythm and a formal inspection point.
When adaptation involves scope changes (adding or removing Product Backlog items), the Product Owner must be involved. The Sprint Goal cannot change, but the scope of work can be clarified and renegotiated. For example:
- If Developers realize they will finish early, they can pull additional items from the Product Backlog in consultation with the Product Owner.
- If Developers realize they have taken on too much, they can negotiate with the Product Owner about which items to remove, always preserving the Sprint Goal.
Exam Tips: Answering Questions on Daily Scrum and Adapting the Sprint Backlog
The PSM II exam requires nuanced, scenario-based thinking. Here are detailed tips for answering questions on this topic:
1. Always prioritize the Scrum Guide.
When in doubt, go back to what the Scrum Guide says. The Daily Scrum is for Developers, it is 15 minutes, and its purpose is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. If an answer contradicts the Scrum Guide, it is wrong — regardless of how practical it might seem.
2. Remember that the Developers own the Daily Scrum.
Any answer that suggests the Scrum Master runs, facilitates, or controls the Daily Scrum is likely incorrect. The Scrum Master ensures it happens and coaches on effectiveness, but the Developers decide how to conduct it.
3. The Daily Scrum is a planning event, not a reporting event.
Look for answers that emphasize creating a plan for the next 24 hours and collaborative discussion. Reject answers that focus on individual status updates or reporting to stakeholders.
4. The Sprint Backlog is expected to change.
Answers that treat the Sprint Backlog as fixed after Sprint Planning are incorrect. The plan evolves as Developers learn more. However, the Sprint Goal does not change during the Sprint.
5. Focus on the Sprint Goal.
The Sprint Goal is the lens through which all Daily Scrum discussions should be viewed. Any answer that disconnects the Daily Scrum from the Sprint Goal is likely wrong.
6. The three questions are optional.
If a question implies that the three-question format is mandatory, that answer is incorrect. The Developers choose their own format.
7. Look for self-management.
PSM II heavily tests the concept of self-managing teams. Answers that promote Developers making their own decisions about how to organize work, adapt the Sprint Backlog, and conduct the Daily Scrum are generally correct.
8. Stakeholders and managers do not attend or direct the Daily Scrum.
While it is not explicitly forbidden for others to observe, the Daily Scrum is for the Developers. Any answer that suggests a manager, stakeholder, or even the Product Owner (in a directing capacity) controls the event is incorrect.
9. Impediment removal is the Scrum Master's service, not the Daily Scrum's purpose.
The Daily Scrum may surface impediments, but its purpose is not impediment removal. The Scrum Master takes note of impediments and works to resolve them, but the Daily Scrum should not be consumed by problem-solving.
10. Watch for scenario-based nuances.
PSM II questions often present complex scenarios. Read carefully. A question might describe a team that is highly collaborative and communicates constantly, then ask if they still need a Daily Scrum. The answer is yes — the Daily Scrum provides a formal inspection point that informal communication cannot replace.
11. Understand the relationship between adaptation and negotiation.
When Developers need to change the scope of the Sprint Backlog (add or remove Product Backlog items), they negotiate with the Product Owner. However, they do not need the Product Owner's permission to adjust how they do the work — that is entirely within the Developers' authority.
12. Consider the bigger picture of empiricism.
The Daily Scrum is one of several inspection and adaptation opportunities in Scrum. At the PSM II level, you should understand how it fits into the broader framework: Sprint Planning inspects and adapts at the Sprint level, the Daily Scrum does so daily, the Sprint Review inspects the product, and the Sprint Retrospective inspects the process. Being able to articulate this flow demonstrates mastery.
Summary
The Daily Scrum is a vital daily inspection and adaptation event owned by the Developers. Its purpose is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog accordingly. The Sprint Backlog is a living plan that evolves throughout the Sprint as the Developers learn more about the work. The Scrum Master supports the effectiveness of the Daily Scrum through coaching but does not lead it. For the PSM II exam, focus on the principles of self-management, empiricism, and the Sprint Goal as the guiding light for all Daily Scrum conversations. Avoid answers that suggest rigid formats, status reporting, or external control over the Developers' planning process.
