At a Sprint Review a stakeholder proposes an integration with his reporting tool. Two Developers say it looks like a week of work, the head of sales says it should go straight to the top, and the Scrum Master is asked to write the decision down. Who decides whether the integration enters the Product Backlog and where it sits?

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 The attendees together, since the Sprint Review is where the Scrum Team and stakeholders collaborate on what to do next

Wrong, and it is the strongest distractor here because the collaboration is real and the Product Backlog genuinely may be adjusted during the event. But collaboration is the input; the ordering decision that comes out of it belongs to one accountability.

Correct The Product Owner, who is accountable for creating Product Backlog items and for ordering them

Correct. Both halves of the question — whether it goes in at all and where it goes — are the same accountability, exercised in the open at the Review rather than afterwards in private.

Not correct The Developers, because they are the ones who know what the integration costs

Wrong. The Developers who will be doing the work are responsible for the sizing, and what they say a thing costs is a serious input, but cost is not value and sizing is not ordering.

Not correct The head of sales, as the most senior person present and the one answerable for revenue

Wrong, and inverted. Scrum's requirement runs the other way: for Product Owners to succeed, the entire organisation must respect their decisions — seniority does not acquire the Product Backlog.

Why

A Sprint Review is a room full of legitimate opinions and one accountable decision-maker, and PSM I loves the gap between those. Stakeholders supply what changed in their world, Developers supply what things cost, and the Product Owner converts both into content and order in the Product Backlog. Nothing about collaborating on what to do next hands the ordering to the room, and nothing about seniority moves it either.

Where this comes from

Cited
Scrum Guide section Product Owner
What it says
Ordering Product Backlog items

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