One product is built by three Scrum Teams. Each team has kept its own Product Backlog and its own Product Owner, and the three Product Owners meet monthly to align. Releases keep clashing and nobody in the organisation can say what the single most valuable next thing for the product is. What does Scrum say about this structure?

Professional Scrum Master I, objective 3. Managing products with agility 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

Not correct It works as long as the three Product Owners agree a common ordering at their monthly alignment meeting

Wrong. Three lists reconciled once a month are still three lists: between meetings each team orders locally, and no one position in any of them is a statement about the product as a whole.

Not correct It works once a chief Product Owner is appointed above the three to arbitrate between their backlogs

Wrong. Scrum defines no chief Product Owner and no hierarchy of Product Owners; inventing a tier above the three leaves the three backlogs in place and adds a role the framework does not contain.

Correct Multiple Scrum Teams working on the same product should share the same Product Goal, Product Backlog and Product Owner

Correct. The Guide says this directly about teams on one product, and it is what makes an ordering mean anything: one list in which every piece of work competes with every other.

Not correct The split is required, because one Product Owner may not serve more than one Scrum Team

Wrong. Nothing in Scrum caps how many teams a Product Owner may serve; the constraint runs the other way, tying one product to one backlog and one Product Owner.

Why

An ordering only carries information if everything that competes for the same product's capacity sits in the same list. Split the product across three backlogs and each is honestly ordered against itself while the product-level trade-off — this team's third item against that team's first — never gets made by anyone. That is why the Guide's own answer to a team that has grown too big is to reorganise into several teams around the same Product Goal, Product Backlog and Product Owner, rather than to divide the backlog with the people.

Where this comes from

Cited
Scrum Guide section Scrum Team
What it says
Therefore, they should share the same Product Goal, Product Backlog, and Product Owner.

Practise this

Reading one question is not practice. The trainer will draw a set from objective 3 and space the ones you get wrong.

Practise Professional Scrum Master I

More questions on this objective

All questions on Managing products with agility