On day six of a two-week Sprint a payment fix meets the Definition of Done and the Product Owner judges that customers need it now rather than in nine days. The release engineer says nothing can ship until the Sprint Review on day ten. What does Scrum say?

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

Correct An Increment may be delivered to stakeholders before the end of the Sprint, so the fix can go out on day six

Correct. Once work meets the Definition of Done an Increment exists, and Scrum places no waiting period between that moment and delivering it to the people who need it.

Not correct The fix must wait for the Sprint Review, where the sum of the Sprint's Increments is presented to stakeholders

Wrong, and it is tempting because the sum of the Increments really is presented at the Sprint Review. Presenting the work and releasing it are separate things; the Review inspects, it does not authorise.

Not correct The fix may go out early only if the Scrum Team first cancels the Sprint and starts a new one

Wrong. Cancellation is for a Sprint Goal that has become obsolete, and it is the Product Owner's authority alone. Nothing about an early release requires or justifies it.

Not correct The fix may go out early only if the Developers agree unanimously to break the Sprint boundary

Wrong. Releasing mid-Sprint breaks nothing — the Sprint is a container for the work and its events, not a hold on delivery — and release timing is not a Developer vote.

Why

The Sprint is a timebox for inspection and adaptation, not an embargo on value. The moment an item meets the Definition of Done an Increment is born, and Scrum explicitly allows it to reach stakeholders before the Sprint ends. The mechanism worth carrying: the Sprint boundary governs when the team inspects and re-plans, while the Definition of Done governs when something is releasable.

Where this comes from

Cited
Scrum Guide section Increment
What it says
However, an Increment may be delivered to stakeholders prior to the end of the Sprint.

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