Confused with product goals
From the onset, I prefer to say I am a beginner, so if my thoughts are wrong, please correct me.
I believe we have to say product vision -> product strategy -> product goal; from that goal, we can have many other product objectives.
I went through the PSM I curriculum and was accustomed to a single product goal that translates to a product backlog.
After going through the PSPO I curriculum, I see that there can be many product goals.
(see image enclosed in link below)
It doesn't sound very clear to me. I prefer a single product goal and then multiple product objectives. This aligns with OKR, which is very common in companies.
to be concrete, here's an example of how I see this
product vision: help busy parents with meal planning for their family
Product goal: Build a meal planning and recipe app that helps parents discover, plan, and cook healthy meals for their families.
Product Backlog:
Epic 1: Recipe Discovery
User Story 1.1: As a user, I want to search for recipes by type (e.g., vegetarian, gluten-free) so I can find meals that fit my preferences for my family.
Epic 2: Meal planning
User Story 2.1: As a user, I want to see a weekly calendar view of my meal plan so I can easily visualize and adjust my meals.
Product objectives:
Quarter 1:launch MVP with at least 1000 early adopters
Quarter 2: increase early adopters satisfaction rate to 8/10 on average.
In summary:
There is a single goal for a product and multiple objectives, not multiple product goals. It's just a language confusion, which I think can increase clarity if we change it.
I was just thinking out loud. Thanks
A Product Backlog ought to have one Product Goal at a time.
The Scrum Guide says: "The Product Goal is the long-term objective for the Scrum Team. They must fulfill (or abandon) one objective before taking on the next."
The Scrum Guide advocates for one active Product Goal at a time, which can evolve or change as the product and circumstances change. The PSPO curriculum complements this by adding additional layers, such as a Product Vision and Product Strategy, which provide broader context and may include multiple sequential Product Goals. Within Scrum, however, only one of these Product Goals is active at a time, and the Product Backlog is focused on that active goal.