Coaching Product Owners as a Scrum Master

The Scrum Master-Product Owner Relationship

The 2020 Scrum Guide states that the Scrum Master serves the Product Owner by helping find techniques for effective Product Goal definition and Product Backlog management, helping the team understand the need for clear and concise Product Backlog items, and facilitating stakeholder collaboration.

In practice, most Scrum Masters either ignore the PO entirely (focusing only on the dev team) or overstep by making product decisions. The sweet spot is coaching — helping the PO become more effective without taking ownership of their accountability.

Where Product Owners Struggle

Based on patterns across enterprise Agile teams, POs commonly struggle with:

Backlog management:

• Backlog grows endlessly without pruning
• Items lack clear acceptance criteria
• Priority changes every sprint without explanation
• No visible connection between backlog items and product strategy

Stakeholder management:

• Saying yes to every request without prioritisation
• Not communicating trade-offs to stakeholders
• Allowing stakeholders to bypass the backlog and go directly to developers
• Failing to set expectations about delivery timelines

Value articulation:

• Writing stories that describe solutions rather than problems
• Not defining measurable success criteria
• Prioritising by loudest stakeholder rather than highest value
• No product vision or roadmap connecting daily work to strategy

Coaching Techniques

1. Backlog Health Coaching

Help the PO maintain a healthy backlog through regular coaching conversations:

The "Top 10" check: Every refinement, ask: "If we could only deliver 10 items this quarter, which would they be?" This forces ruthless prioritisation and surfaces items that have been sitting in the backlog without real intent to deliver.

The acceptance criteria workshop: When stories lack clear criteria, facilitate a "Three Amigos" session (PO, developer, tester) to define what done looks like before the story enters a sprint.

The backlog pruning ritual: Monthly, review items older than 3 months. If they haven't been prioritised into a sprint in 90 days, they're probably not important. Archive or delete them.

The dependency flag: Help the PO identify items that depend on other teams or external systems. These need earlier visibility and coordination — they can't be treated like independent stories.

2. Stakeholder Coaching

Help the PO build stronger stakeholder relationships:

The intake process: Coach the PO to establish a formal intake process for new requests. Every request gets captured, sized, and prioritised against existing work — not immediately committed to.

The trade-off conversation: When a stakeholder asks for something new, coach the PO to respond with: "We can do that. What should we deprioritise to make room?" This makes the cost of new requests visible.

The Sprint Review as stakeholder tool: Help the PO use Sprint Review not just as a demo, but as a feedback-gathering and expectation-setting event. Stakeholders should leave knowing what's coming next and what's been deprioritised.

The "no" framework: Many POs struggle to say no. Coach them to reframe: "Not now" is easier than "no." Help them communicate priority order rather than binary yes/no decisions.

3. Value Coaching

Help the PO focus on outcomes over output:

The "so what?" test: For every feature request, ask: "If we ship this, what changes for the user? How will we know it worked?" If the PO can't answer, the item needs more discovery before development.

Outcome-based roadmapping: Coach the PO to express the roadmap in terms of outcomes ("reduce checkout abandonment by 20%") rather than features ("add Apple Pay"). This gives the team room to find the best solution.

Data-informed prioritisation: Help the PO establish metrics for feature success. After shipping, review: did the feature achieve its intended outcome? This builds a feedback loop that improves future prioritisation.

When to Coach vs When to Step Back

Coach when:

• The PO asks for help or is visibly struggling
• The team is affected by PO decisions (unclear stories, constant priority changes)
• Patterns repeat across multiple sprints (same problems recurring)
• The PO is new to the role and building skills

Step back when:

• The PO is making product decisions (that's their accountability)
• Stakeholders are debating business priorities (facilitate, don't decide)
• The PO has a clear approach and is executing well
• You disagree with a prioritisation decision but the PO has valid reasoning

Measuring PO Effectiveness

Track these indicators over time (share with the PO as coaching data, not as a performance score):

• Backlog health: % of top-20 items with clear acceptance criteria
• Refinement effectiveness: % of items entering sprint that need no further clarification
• Sprint Goal clarity: Can every team member articulate the Sprint Goal?
• Stakeholder satisfaction: Quarterly pulse — do stakeholders feel heard and informed?
• Feature adoption: % of shipped features actually used by customers
• Story rejection rate: How often does the team push back on unclear items in planning?

The Coaching Conversation Framework

Use this structure for regular 1:1 coaching sessions with the PO (fortnightly works well):

1. What's working? Start positive — acknowledge what the PO is doing well 2. What's challenging? Let the PO surface their own struggles 3. What patterns do you notice? Share observations from ceremonies (not judgments) 4. What would you like to try? Help the PO identify one experiment for the next sprint 5. How can I support? Offer specific help — facilitation, stakeholder conversations, tooling

Keep it to 30 minutes. One improvement per session is enough. Sustainable change comes from consistent small steps, not dramatic overhauls.

---

Download the [Sprint Health Check template](/templates) to track backlog health indicators alongside delivery metrics.