Study guide

3.5 How the Scrum Team Interacts Across a Sprint

Certified ScrumMaster CSM

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Agile Foundations, Scrum Theory & Empirical Process Control

1.1 Agile Manifesto & Lean Thinking 1.2 Empirical Process Control 1.3 Complex Adaptive Systems & Cynefin Framework 1.4 Scrum Framework Overview & Core Rules 1.5 Iterative & Incremental Delivery 1.6 Partial Scrum Adoption & Its Consequences

2 Chapter 2: The Five Scrum Values & Cultural Mindset

2.1 Commitment & Focus 2.2 Openness & Respect 2.3 Courage & Ethical Leadership

3 Chapter 3: Scrum Team Accountabilities & Dynamics

3.1 Developers Accountability & Self-Management 3.2 Product Owner Accountability & Business Value 3.3 Scrum Master Accountability & Servant Leadership 3.4 Team Characteristics, Size & Cross-Functionality 3.5 How the Scrum Team Interacts Across a Sprint 3.6 Why Scrum Has No Project Manager

4 Chapter 4: The Five Scrum Events & Timeboxing

4.1 The Sprint Container & Goal Preservation 4.2 Sprint Planning Event 4.3 Daily Scrum Event & Micro-Planning 4.4 The Sprint Review 4.5 The Sprint Retrospective 4.6 Effects of Skipping the Sprint Retrospective 4.7 Choosing a Suitable Sprint Length 4.8 Inspect & Adapt at Every Scrum Event

5 Chapter 5: Scrum Artifacts, Commitments & Definition of Done

5.1 Product Backlog & Product Goal 5.2 Sprint Backlog & Sprint Goal 5.3 Increment & Definition of Done 5.4 Multi-Team DoD & Technical Debt Management 5.5 Product Backlog Refinement 5.6 Product Backlog Item Attributes & Ordering 5.7 Creating & Evolving the Definition of Done

6 Chapter 6: Scrum Master Core Competencies, Servant Leadership & Coaching

6.1 Facilitation & Professional Coaching Techniques 6.2 Removing Impediments & Root Cause Analysis 6.3 Servant Leadership & Organizational Change 6.4 Agile Metrics, Velocity Traps & Scaling Basics 6.5 Development Practices That Protect the Increment 6.6 Serving the Product Owner 6.7 Organizational Design Change from Adopting Scrum

7 Chapter 7: The CSM Test — Format, Logistics & Official Blueprint

7.1 CSM Test Format & Scoring 7.2 Course Prerequisite, Attempts & Renewal 7.3 The Official Learning Objectives Blueprint

3.5 How the Scrum Team Interacts Across a Sprint

Key Takeaways Explain This Topic AI

Scrum Foundations LO 2.1 asks you to illustrate how the Product Owner, Developers, and Scrum Master interact to deliver Increments within a Sprint — a sequence question, not a definitions question.

The three accountabilities are peers: there is no hierarchy among them and no reporting line from Developers to the Scrum Master or Product Owner.

The Product Owner's heaviest involvement is at the boundaries — Sprint Planning Topic One and the Sprint Review — plus continuous availability for refinement and scope renegotiation.

The Developers own everything inside the Sprint: the Sprint Backlog, the daily plan, and how items become an Increment.

If the Product Owner or Scrum Master works on Sprint Backlog items, they participate in the Daily Scrum as Developers, not as observers.

Last updated: August 2026

Quick Answer: Across one Sprint the Product Owner brings why and what (value, ordering, the proposal that opens Sprint Planning), the Developers own how much and how (selection, the Sprint Backlog, the daily plan, the Increment), and the Scrum Master owns the effectiveness of the whole (events happen, are productive and timeboxed; impediments get removed; self-management is coached). No one directs anyone else.

Scrum Foundations Learning Objective 2.1 asks candidates to illustrate how the product owner, developers and scrum master interact to deliver increments within a sprint . That verb — illustrate — is why memorizing three separate accountability lists is not enough. You need the choreography.

The Structural Rule That Governs Every Interaction

The Scrum Guide is unambiguous: "Within a Scrum Team, there are no sub-teams or hierarchies." The Scrum Master is not the Developers' manager. The Product Owner is not the Scrum Master's client. All three are members of one cohesive unit, and the entire Scrum Team — not the Developers alone — is accountable for creating a valuable, useful Increment every Sprint.

This single rule resolves most CSM scenario questions. Whenever an option has one accountability instructing another, it is almost certainly wrong.

Walking One Sprint End to End

Moment in the Sprint Product Owner Developers Scrum Master

Before Sprint Planning Orders the Product Backlog; ensures top items are understood and ready Participate in refinement; size items Helps the PO find techniques for effective Product Backlog management

Sprint Planning — Topic One (Why) Proposes how the product could increase value this Sprint Collaborate on shaping the Sprint Goal Ensures the event happens, stays within eight hours for a one-month Sprint, and is productive

Sprint Planning — Topic Two (What) Discusses items, clarifies, negotiates trade-offs Select the items to bring into the Sprint Coaches against pressure to over-commit

Sprint Planning — Topic Three (How) Not involved in the technical plan Decompose work and create the Sprint Backlog Ensures nobody outside the Developers dictates the plan

Daily Scrum Attends only if working on Sprint Backlog items — then as a Developer Inspect progress toward the Sprint Goal; replan the next day's work Ensures the event happens and stays within 15 minutes; coaches the Developers to run it themselves

During the Sprint Available for questions; renegotiates scope as more is learned; refines the backlog with the team Build the Increment; adapt the Sprint Backlog; hold each other accountable Causes the removal of impediments; protects the team from disruption

Sprint Review Leads the discussion of progress toward the Product Goal; adapts the Product Backlog Present the Done Increment; answer questions; discuss what changed Ensures the event is a working session, not a passive demo, and stays within four hours for a one-month Sprint

Sprint Retrospective Participates as a full Scrum Team member Participate as full Scrum Team members Facilitates; ensures the event produces actionable improvements

The Three Interfaces the Exam Tests

1. Product Owner ↔ Developers — the scope interface. The Product Owner decides what is most valuable ; the Developers decide how much fits and how it gets built . Mid-Sprint, scope "may be clarified and renegotiated with the Product Owner as more is learned" — a two-way negotiation, never a one-way instruction. The invariant is the Sprint Goal: negotiation may reshape scope but must not endanger the goal.

2. Scrum Master ↔ Developers — the coaching interface. The Scrum Master coaches self-management and cross-functionality and causes impediments to be removed. The Scrum Master does not assign tasks, does not run the Daily Scrum as a status round, and does not update the Sprint Backlog on the team's behalf.

3. Scrum Master ↔ Product Owner — the service interface. The Scrum Master helps the Product Owner find techniques for effective Product Goal definition and Product Backlog management, helps the team understand the need for clear and concise items, helps establish empirical product planning, and facilitates stakeholder collaboration as requested or needed. Support, not substitution — the Scrum Master never orders the backlog.

The Dual-Participation Rule

A detail the test likes: if the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they participate in the Daily Scrum as Developers. They do not attend as observers with a special status. This is the practical expression of "no sub-teams or hierarchies" — accountability is defined by the work being done, not by a job title.

Real-World CSM Scenario

Three days into a two-week Sprint, the Product Owner asks the Developers to add a small reporting feature that a major customer requested that morning.

The correct choreography: the Product Owner explains the value and the customer context. The Developers assess whether the addition endangers the Sprint Goal and what would have to come out to make room — that assessment is theirs, not the Product Owner's. Together they renegotiate the scope of the Sprint Backlog while leaving the Sprint Goal intact. If the request genuinely cannot fit without endangering the goal, it goes to the Product Backlog for a future Sprint.

The Scrum Master's part is the smallest and the most easily misplayed: they do not decide, do not veto, and do not carry the message between the parties. They ensure the conversation actually happens between the people accountable for it, and afterwards coach the Product Owner on routing customer requests through refinement so mid-Sprint interruptions become rarer.