Answering: “When must a Scrum Team release each Increment?” (PSM I)

A Scrum Team releases an Increment when it makes sense to release it. Scrum requires a usable Increment every Sprint, not a release every Sprint.

Exam Question

When must a Scrum Team release each Increment?
(choose the best answer)
A. After every Sprint, without exception.
B. When the Scrum Team finishes their work.
C. When it makes sense to release it.
D. Whenever the product is free of defects.

Correct Answer

C. When it makes sense to release it.

Why This Is the Correct Answer

Every Sprint must produce at least one Increment that meets the Definition of Done, so it is usable and could be released. Whether to actually release it is a business decision, usually led by the Product Owner, based on value, market timing and stakeholder needs. The Scrum Guide notes that “Multiple Increments may be created within a Sprint” and that an Increment “may be delivered to stakeholders prior to the end of the Sprint.” It also says “The Sprint Review should never be considered a gate to releasing value.” So releases can happen several times a Sprint, once per Sprint, or after several Sprints.

Why the Other Options Are Wrong

A. After every Sprint, without exception. Scrum requires a releasable Increment, not a release. Sometimes holding an Increment back makes business sense.

B. When the Scrum Team finishes their work. Product work is never really finished, and release timing should follow value, not the team’s workload.

D. Whenever the product is free of defects. No product is ever entirely free of defects. Quality is governed by the Definition of Done, and release is a value decision.

Exam Tip

Keep “releasable” and “released” apart. Scrum demands the first every Sprint and leaves the second to judgment about value.

Key Takeaways

• Every Sprint must produce a usable Increment.
• Release timing is a business decision.
• Increments can be released before the Sprint Review.