Product Goals: One or Many?
I have to say I am a bit confused on this point.
The Scrum Guide suggests that there should only be one Product Goal and at any one time.
“The Product Goal is the long-term objective for the Scrum Team. They must fulfill (or abandon) one objective before taking on the next”
However, the Scrum.org Learning Series suggest multiple Product Goals:
“Product Goals are hypotheses that a Scrum Team uses to progress toward their Product Vision. They can change as the team learns more about stakeholder and customer needs”
So two questions:
1. Do we think it is advantageous to hold multiple Product Goals?
2. I am currently helping people to pass their PSM exams and not sure what to tell them.
There can be as many Goals for a Product as are valuable, but only one at a time.