PSM I Customers, Stakeholders, and Feedback

Scrum treats feedback as a product asset, not as a disruption to be minimized. PSM I questions in this area often test whether you can use stakeholder and customer learning to improve Product Backlog decisions without collapsing Sprint focus or bypassing the Product Owner.

Feedback rules

What stronger answers protect

The stronger answer usually keeps three things true at once:

• the Product Owner remains accountable for product value decisions
• stakeholders still have real opportunities to inspect and influence product direction
• the Sprint stays coherent instead of turning into a stream of unmanaged interrupts

Example

At the Sprint Review, stakeholders identify a new customer need that changes product priorities. The stronger answer is to adapt the Product Backlog for future work, not to quietly inject new work into the Sprint without inspecting its effect on the Sprint Goal.

Common pitfalls

• Treating stakeholder feedback as interference.
• Treating every new request as immediate Sprint scope.
• Confusing openness to learning with lack of focus.
• Assuming the Product Owner is a message relay rather than the value decision maker.

Sample Exam Question

What is the strongest Scrum response when stakeholder feedback changes product priorities?

A. Adapt the Product Backlog based on the new learning while preserving clear Product Owner accountability
B. Let stakeholders add work directly to the Sprint Backlog so the team stays responsive
C. Delay all feedback until the release is complete so the team can avoid churn
D. Ask the Scrum Master to reorder the Product Backlog because facilitation is part of the role

Best answer: A

Why: Scrum uses stakeholder learning to improve future decisions, but it keeps product accountability and Sprint coherence intact.

Why the others are weaker: B, C, and D either bypass accountabilities or reduce empiricism.