Study guide

5.2 Stakeholders & Customers

Professional Scrum Master I PSM I

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & Scrum Fundamentals

About the PSM I Exam How to Use This Course 1.1 Scrum Theory & Empiricism 1.2 The Five Scrum Values 1.3 The Scrum Team Overview 1.4 Scrum Definition, Rules, & Boundaries

2 Chapter 2: Scrum Accountabilities & Team Dynamics

2.1 The Developers Accountability & Technical Ownership 2.2 The Product Owner Accountability & Value Maximization 2.3 The Scrum Master Accountability & True Leadership 2.4 Self-Managing Teams & 2020 Scrum Guide Evolution 2.5 Cross-Functional Teams & Skill Diversity 2.6 Leadership Stances of the Scrum Master

3 Chapter 3: Scrum Events & Timeboxing

3.1 The Sprint Event & Container Nature 3.2 Sprint Planning Event (Three Topics) 3.3 Daily Scrum Event & 15-Minute Timebox 3.4 Sprint Review Event & Stakeholder Feedback 3.5 Sprint Retrospective Event & Continuous Improvement 3.6 Event Facilitation & Conflict Resolution

4 Chapter 4: Scrum Artifacts & Commitments

4.1 Product Backlog Artifact & Refinement 4.2 Product Goal Commitment 4.3 Sprint Backlog Artifact & Ownership 4.4 Sprint Goal Commitment 4.5 Increment Artifact & Definition of Done Commitment 4.6 Definition of Done vs. Acceptance Criteria

5 Chapter 5: Agile Product Management & Team Leadership

5.1 Product Backlog Management & Ordering Strategies 5.2 Stakeholders & Customers 5.3 Product Value Metrics & Evidence-Based Management (EBM) 5.4 Agile Forecasting & Release Planning 5.5 Psychological Safety & Impediment Removal 5.6 Scaling Scrum Fundamentals & Nexus Overview

5.2 Stakeholders & Customers

Key Takeaways Explain This Topic AI

Scrum.org lists Stakeholders & Customers as a Managing Products with Agility focus area for PSM I.

The Scrum Team is responsible for stakeholder collaboration as part of product-related activities, not only during demos.

The Sprint Review is a working session where the Scrum Team and key stakeholders inspect the Increment and adapt the Product Backlog.

The Product Owner remains accountable for ordering even when Developers converse directly with stakeholders.

Transparent artifacts and a usable Done Increment make stakeholder feedback empirical instead of opinion-based.

Last updated: July 2026

5.2 Stakeholders & Customers

Why this matters for PSM I: Scrum.org lists Stakeholders & Customers as an explicit focus area under Managing Products with Agility. Many candidates only study Sprint Review mechanics and miss the broader accountability: the Scrum Team continuously collaborates with stakeholders, and the Product Owner steers value decisions using customer and market signals — not internal preference alone.

In the 2020 Scrum Guide, the Scrum Team is responsible for all product-related activities from stakeholder collaboration , verification, maintenance, operation, experimentation, research and development, and anything else required to create a valuable product. Stakeholders and customers are therefore not "optional guests" — they are part of the empirical feedback loop that makes Scrum work.

Stakeholders vs. Customers (Clear Distinctions)

Term Practical meaning in Scrum contexts Typical examples

Customer The person or group who uses or buys the product / receives value from the Increment End users, paying clients, internal consuming teams

Stakeholder Anyone with a material interest in the product outcome or constraints Sponsors, regulators, sales, support, security, partner teams, executives

Product Owner Single accountability maximizing product value and managing the Product Backlog Represents stakeholder needs in ordering decisions

Scrum Team Whole team accountable for valuable Increments and stakeholder collaboration PO + SM + Developers collaborating with stakeholders

PSM I scenarios often blur these labels on purpose. The correct answer usually protects three ideas at once: (1) value is judged empirically with real feedback, (2) the Product Owner remains accountable for ordering, and (3) stakeholders inspect outcomes frequently enough to enable adaptation.

  • Where Stakeholder Collaboration Happens
  • 1. Continuously — Not Only at Sprint Review

The Guide does not confine stakeholder interaction to a single ceremony. Product Backlog ordering, discovery conversations, release decisions, and risk trade-offs all require stakeholder input. Waiting until the last day of the Sprint to "show stakeholders something" is a common anti-pattern that delays inspection and adaptation.

2. Sprint Review — Formal Inspection Point

The Sprint Review is the formal event where the Scrum Team and key stakeholders inspect the outcome of the Sprint and determine future adaptations. Progress toward the Product Goal is discussed. The Product Backlog may be adjusted to meet new opportunities. This is a working session , not a one-way demo.

3. Product Owner Representation Between Events

Between Reviews, the Product Owner is accountable for maximizing value. That includes engaging stakeholders and customers to understand needs, constraints, and desirability — then reflecting those insights in Product Backlog order and Product Goal alignment. Developers may talk directly with stakeholders when helpful; the Product Owner still owns ordering accountability.

4. Scrum Master Service to Stakeholder Collaboration

The Scrum Master serves the Product Owner by facilitating stakeholder collaboration as requested or needed, and helps the organization understand empiricism. When stakeholders are unavailable, hostile to transparency, or try to bypass the Product Owner, the Scrum Master coaches the organization toward healthier collaboration patterns.

Transparency Enables Useful Stakeholder Feedback

Stakeholders cannot give meaningful feedback on opaque work. Artifact commitments exist partly so outsiders can inspect reality:

Product Goal communicates the long-term product target stakeholders can understand.

Definition of Done makes "complete" transparent so stakeholders do not confuse unfinished work with a usable Increment.

Increment must be usable — stakeholders inspect actual product behavior, not slideware promises.

Product Backlog remains the single source of work; side lists maintained for individual stakeholders destroy transparency.

If stakeholders demand status outside these transparent artifacts, the Scrum Master helps the organization use Scrum's information radiators instead of inventing parallel reporting theater.

Exam Scenarios: Typical Stakeholder Traps

Trap Why it fails Scrum Better Scrum response

Stakeholders assign work directly to Developers mid-Sprint Breaks Product Owner ordering and Sprint Goal focus Route requests through Product Owner; protect Sprint Goal

Sprint Review becomes a PowerPoint status meeting No real inspection of Increment; weak adaptation Inspect Done Increment; collaborate on backlog adaptations

Product Owner hides unfinished work "until perfect" Delays empiricism; stakeholders cannot adapt Show usable Done Increment; learn early

Multiple "business owners" reorder the backlog independently No single Product Owner accountability One Product Owner accountable for ordering

Customers only engaged after release train ships Feedback arrives too late for Sprint-level adaptation Invite key stakeholders to Reviews; validate assumptions earlier

Customers, Value, and Empiricism

Managing products with agility means value hypotheses are tested with customer evidence. Forecasts and release plans are useful only when stakeholder/customer feedback can invalidate assumptions quickly. The Product Owner may use complementary discovery techniques, but PSM I answers still center on:

Frequent delivery of Done Increments so customers can respond to real product behavior.

Product Backlog adaptation when stakeholder insight changes priorities.

One Product Goal at a time so stakeholder conversations stay coherent rather than thrashing across competing strategies.

A Scrum Master who "protects the team from all stakeholders" can accidentally create an information silo. Healthy boundaries protect the Sprint Goal from interruption, while still enabling the collaboration the Guide requires.

Practical Collaboration Patterns (Complementary, Not Mandated)

Scrum does not prescribe a stakeholder map template. Common complementary practices include stakeholder mapping, customer interviews, usability tests, and release demos outside the Sprint Review. On the exam, remember: complementary practices can help, but they never replace Product Owner accountability, Definition of Done, or the Sprint Review's inspect-and-adapt purpose.

Summary

Stakeholders and customers close Scrum's empirical loop. The Scrum Team collaborates with them continuously; the Sprint Review is the formal inspection checkpoint; the Product Owner turns their signals into ordered backlog decisions; and the Scrum Master enables collaboration and transparency. Treat "Stakeholders & Customers" as a first-class PSM I focus area — not a footnote of the Sprint Review.

Loading diagram... Product Goal Hierarchy and Stepping Stones