Overview

• What you’ll learn: Who stakeholders are, how the PO manages their expectations, the role of Sprint Review in stakeholder engagement, and techniques for saying “not yet” constructively.
• Prerequisites: Lesson 10 — The Product Owner.
• Estimated reading time: 12 minutes

Introduction

Stakeholders are everyone who has an interest in the product but is not part of the Scrum Team. This includes customers, end users, executives, sales teams, support teams, compliance officers, and that one VP who has “a great idea” every Tuesday. Managing their expectations is one of the PO’s most challenging and critical responsibilities.

The Stakeholder Landscape

The Art of Saying “Not Yet”

The PO cannot say “yes” to everything. The Product Backlog is ordered by value, and items lower on the list may never be built. The key is to communicate this honestly without burning bridges:

• Acknowledge the request: “I understand why this is important to you.”
• Show the backlog: “Here is what we are currently focused on and why.”
• Explain the trade-off: “To do this, we would need to defer X. Is that acceptable?”
• Offer alternatives: “We can do a simpler version that delivers 80% of the value in 20% of the time.”
• Invite to Sprint Review: “Come see what we’ve built and help us decide what to do next.”

Sprint Review as Stakeholder Engagement

The Sprint Review is the primary formal opportunity for stakeholder engagement. During the Review, the Scrum Team presents the Increment, stakeholders provide feedback, and the Product Backlog is adjusted accordingly. This is not a demo — it is a collaborative working session.

Transparency as a Tool

The best stakeholder management tool is transparency. When the Product Backlog is visible and the Product Goal is clear, stakeholders can see where their requests fit. They may not like the priority, but they understand it.

Key Takeaways

• Stakeholders include anyone interested in the product who is not on the Scrum Team.
• The PO manages stakeholder expectations through transparency, communication, and trade-off conversations.
• Sprint Review is the primary stakeholder engagement ceremony — it is collaborative, not presentational.
• Saying “not yet” is better than saying “yes” to everything and delivering nothing well.
• Transparency in the Product Backlog helps stakeholders understand priorities.

What’s Next

In Lesson 16, you will explore scaling Scrum — what happens when multiple teams work on the same product, and how to maintain one Product Backlog and one Product Owner.