A Product Owner is handed two systems with different user bases, different customers and separate budgets, and told to treat them as one product with a single Product Goal. She asks the Scrum Master what Scrum actually means by a product. Which answer matches the Guide?

Professional Scrum Master I, objective 3. Managing products with agility easy

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 A product is a vehicle to deliver value with a clear boundary, known stakeholders and well-defined users or customers — so the boundary and the people served are what settle it, not the org chart

Correct. The definition is written in terms of value, boundary and the people served, and two systems with separate customers and no shared boundary do not satisfy it as one thing.

Not correct A product is whatever the organisation funds and reports on as a single line, since that is what the Product Goal must serve

Wrong. Funding structure is an accounting boundary, not a product boundary, and the two coincide only by luck.

Not correct A product is whatever a single Scrum Team works on, so one team means one product by definition

Wrong, and it is the tempting one because the two do often line up. Several Scrum Teams may work on one product, sharing a Product Goal, Product Backlog and Product Owner — team count is not what draws the boundary.

Not correct Scrum does not define a product; it defines only Increments and the Product Backlog

Wrong. Scrum does describe what a product is, and it does so in the section on the Product Goal because the Goal is meaningless without a boundary to apply it to.

Why

The Product Goal describes a future state of a product, so the definition of the product decides what the Goal can even mean. Scrum draws that line around value and around people — a clear boundary, known stakeholders, well-defined users or customers — and a product can be a service or something abstract rather than a piece of software. Two unrelated user populations forced under one Product Goal give the Scrum Team an objective that cannot be fulfilled or abandoned as one thing.

Where this comes from

Cited
Scrum Guide section Commitment: Product Goal
What it says
A product is a vehicle to deliver value. It has a clear boundary, known stakeholders, well-defined users or customers.

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