A Scrum Team has three Product Goals pinned to the wall — one for each market segment the product serves — and works toward all three at once. Sprint Goals alternate between them. What does Scrum say about this?
Professional Scrum Master I, objective 1. Understanding and applying the Scrum framework medium
Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.
Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.
The options
Correct The Product Goal is the long-term objective for the Scrum Team, and it must fulfil or abandon one objective before taking on the next
Correct. A single objective at a time is what allows the rest of the Product Backlog to emerge coherently — it is the target everything else is planned against.
Not correct Several Product Goals are fine, provided each one has its own Product Backlog
Wrong twice over. A Scrum Team focuses on one objective at a time, and a product has one Product Backlog. Splitting the backlog splits the view of the product.
Not correct Several Product Goals are fine, provided the Product Owner orders them against each other
Wrong. Ordering three long-term objectives does not make them one direction; it just decides which of three directions gets attention this week. The Product Goal exists to be a single target the team can plan against.
Not correct Each Sprint should have its own Product Goal, chosen at Sprint Planning
Wrong, and it confuses the two goals. Each Sprint has a Sprint Goal. The Product Goal spans many Sprints, and the Sprint Goals are the steps toward it.
Why
The Product Goal describes a future state of the product that the Scrum Team can plan against; it lives in the Product Backlog, and the rest of the Product Backlog emerges to define what will fulfil it. Count the singulars and most artifact questions answer themselves: one product, one Product Backlog, one Product Owner, one Product Goal at a time — and, inside each Sprint, one Sprint Goal.
Where this comes from
- Cited
- Scrum Guide section Commitment: Product Goal
- What it 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.
Practise this
Reading one question is not practice. The trainer will draw a set from objective 1 and space the ones you get wrong.
Practise Professional Scrum Master I
More questions on this objective
- A department is choosing an approach for a product where both the requirements and the technology are poorly understood and keep changing as the team learns. Someone argues for Scrum "because it is founded on empiricism". What does founding an approach on empiricism actually commit the team to? machine-checked
- At the end of a Sprint three items are functionally complete but have not been through the automated test suite the Definition of Done requires. To avoid an awkward conversation the Developers mark them Done on the board and include them in the Sprint Review. Which pillar has been damaged, and what follows from that? machine-checked
- A Scrum Team holds every event on schedule, keeps a burn-down chart and reviews its metrics carefully. For six Sprints running, the same impediment — a two-day wait for a shared test environment — has been named in the Retrospective, and nothing about it has changed. What is the accurate diagnosis? machine-checked
- Mid-Sprint, the Developers discover that a third-party API rate-limits far below what they assumed, which makes the current plan unworkable. One of them suggests carrying on as planned and raising it at the Sprint Retrospective, so the Sprint is not disrupted. What should happen instead? machine-checked
- Which THREE of these statements about Scrum theory are accurate as the framework defines it? machine-checked
- A Developer is fairly sure the design the team agreed last week will not scale. The team is halfway through the Sprint, everyone else seems content, and saying so means an uncomfortable conversation and probably rework. Which Scrum value most directly asks them to speak? machine-checked
All questions on Understanding and applying the Scrum framework