Three Increments are Done and sitting behind a feature flag. The Developers want to release all three tomorrow; the marketing lead wants to hold them until a campaign launches in three weeks. The Scrum Master is asked who settles it. Who decides when the Increments are released?

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 Developers, because they built the Increments and know best whether they are safe to deploy

Wrong, and it is the closest miss. The Developers decide whether the work meets the Definition of Done and how it is built; whether releasing now is the most valuable move is a different question.

Correct The Product Owner, who is accountable for maximising the value of the product resulting from the team's work

Correct. Release timing is a value judgement — now versus with the campaign — and Scrum puts value decisions about the product with the one person accountable for them.

Not correct The Scrum Master, as the person accountable for the Scrum Team's effectiveness

Wrong. Effectiveness means helping the team improve its practices, not making product decisions for it. A Scrum Master who picks release dates has taken the Product Owner's accountability.

Not correct The stakeholders present at the next Sprint Review, by consensus

Wrong. Stakeholders influence the product by informing the Product Owner and the Product Backlog. Handing them the decision replaces one accountable person with a committee, which is exactly what Scrum avoids.

Why

Scrum defines no release-approval step and no committee — so the question resolves through the accountabilities. The Developers decide how the work is built and whether it meets the Definition of Done; the value of the product resulting from that work is the Product Owner's accountability, and the Guide asks the whole organisation to respect her decisions. Holding three Done Increments back for a campaign is a judgement about value, which is why it lands with her rather than with the people who wrote the code or the people waiting for it.

Where this comes from

Cited
Scrum Guide section Product Owner
What it says
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.

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