5.2 Stakeholders & Customers

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)

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

---

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:

1. Frequent delivery of Done Increments so customers can respond to real product behavior.
2. Product Backlog adaptation when stakeholder insight changes priorities.
3. 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.