What a Scrum Master needs to know about the product side without owning it. The Product Goal, how a Product Backlog is ordered and refined, forecasting from past delivery rather than from estimates, working with stakeholders and what changes when one product needs more than one team.
A Product Owner on a search service has published three Product Goals, one for relevance, one for latency and one for a new admin console, and each Sprint Goal now reads as a summary of whatever was selected. What should the Scrum Master raise, and with whom?
AWith the Developers, who craft the Sprint Goal and could craft a sharper one.
BWith the Product Owner, since a Scrum Team holds one Product Goal at a time.
CWith the organisation, since three goals means the product needs more teams.
DWith nobody, since Scrum sets no limit on the number of Product Goals held.