Answering: “The smallest product Increment that is valuable enough to release is one that:”

The smallest Increment worth releasing is one that delivers a single new or improved outcome. Counting features, bug fixes or must-have items measures output, not value.

Exam Question

The smallest product Increment that is valuable enough to release is one that:
(choose the best answer)
A. Delivers a single new or improved outcome.
B. Adds a new feature.
C. Fixes at least one defect.
D. Delivers all “must do” Product Backlog items.

Correct Answer

A. Delivers a single new or improved outcome.

Why This Is the Correct Answer

Value comes from outcomes, meaning a change in what users can achieve or experience. A release that improves even one outcome gives customers something useful and gives the Scrum Team real feedback. Small releases shorten the loop between building something and learning whether it helped. Scrum.org’s Evidence-Based Management guide encourages small steps toward goals, with each step’s outcome measured before deciding the next. A feature that changes nothing for users, or a large batch of must-do items, may never be worth releasing on its own terms or may take far too long to deliver.

Why the Other Options Are Wrong

B. Adds a new feature. A feature is output. It only matters if it improves an outcome for users.

C. Fixes at least one defect. A fix can be valuable, but the rule is about outcomes, not about counting defects.

D. Delivers all “must do” items. Waiting for every must-do item creates large batches and delays feedback. That is the opposite of the smallest valuable release.

Exam Tip

PSPO II questions often contrast outputs and outcomes. When asked what makes something valuable, choose the outcome-focused answer.

Key Takeaways

• Value is measured in outcomes, not features.
• Small releases speed up learning.
• One improved outcome can justify a release.