Answering: “Your stakeholders are very demanding and each of them has at least one feature that they say is essential for the next release. As the Product Owner you have validated that the feature requests are all valid requests and would likely add value to your product. What should you do?”

Release as soon as you can satisfy at least one valuable outcome, even if not every requested feature is in. Waiting for every stakeholder’s must-have delays all value and all feedback.

Exam Question

Your stakeholders are very demanding and each of them has at least one feature that they say is essential for the next release. As the Product Owner you have validated that the feature requests are all valid requests and would likely add value to your product. What should you do?
(choose the best answer)
A. Release when you can satisfy at least a single outcome, even though not all features are implemented.
B. Wait until all essential features are complete before releasing the product.
C. Escalate to the steering committee to make the call.
D. Pick the two most influential stakeholders and satisfy their needs, then release.

Correct Answer

A. Release when you can satisfy at least a single outcome, even though not all features are implemented.

Why This Is the Correct Answer

The Product Owner is accountable for maximizing value, and value only reaches customers when something is released. If every request must be finished first, the release grows large, slow and risky, and no one learns anything until the end. Releasing once a real outcome is met delivers value early and produces feedback that may change what the remaining features should look like. The Scrum Guide also notes that work may be released to stakeholders before the end of the Sprint, so release timing is driven by value, not by a fixed list. The Product Owner orders the other requests on the Product Backlog and explains the choice to stakeholders.

Why the Other Options Are Wrong

B. Wait until every requested feature is complete. This delays value and feedback for everyone. It treats a list of requests as a fixed scope.

C. Escalate to the steering committee. Ordering the Product Backlog and deciding on releases is the Product Owner’s accountability. Escalating gives it away.

D. Satisfy the two most influential stakeholders, then release. Influence is not value. This choice is political rather than based on outcomes.

Exam Tip

When stakeholders all want their item first, the Scrum.org answer is usually to release small, outcome-focused Increments and keep ordering the rest by value.

Key Takeaways

• Release when an outcome is met, not when the list is empty.
• Early releases bring early feedback.
• The Product Owner owns ordering and release decisions.