Value, Releases & Forecasting

What is the Product Goal in Scrum?

• A A detailed list of every feature for the year
• B The budget allocated to the product
• C The team's velocity target
• D A future state of the product that serves as a long-term objective for the Scrum Team ✓

Answer: The Product Goal describes a future state of the product and is the long-term objective for the Scrum Team; the team must fulfil or abandon one objective before taking on the next.

According to the Scrum Guide, when can a 'Done' Increment be released?

• A Only at the end of the final Sprint of a release
• B Only after the Sprint Review
• C As soon as it meets the Definition of Done, even during the Sprint, at the Product Owner's discretion ✓
• D Only once all Product Backlog items are complete

Answer: Multiple Increments may be created within a Sprint, and a Done Increment is usable; the decision to release it can be made at or before the Sprint Review, at the Product Owner's discretion.

What is the role of the Definition of Done with respect to the value of an Increment?

• A It lists the order of Product Backlog items
• B It sets the Sprint length
• C It is optional documentation
• D It is the formal description of the state of the Increment when it meets the quality measures required for the product, making work potentially releasable ✓

Answer: The Definition of Done is a formal description of the state of the Increment when it meets the required quality measures; work that does not meet it cannot be released or presented as Done.

Which approach to forecasting is most consistent with Scrum's empirical foundation?

• A Committing to a fixed scope and date set 12 months in advance with no change
• B Using historical data and trends, such as past throughput or burn-downs, while accepting forecasts will be refined as more is learned ✓
• C Refusing to forecast at all
• D Letting stakeholders set velocity targets the team must hit

Answer: Empiricism relies on inspecting actual results; forecasting using historical data and trends, then adapting as more becomes known, fits Scrum better than a fixed long-range plan treated as a guarantee.

A Product Owner wants to measure whether the product is actually delivering value to users. Which is the most appropriate focus?

• A The number of items in the Product Backlog
• B Lines of code written per Sprint
• C Number of meetings attended
• D Outcome-based measures such as customer satisfaction, usage and business results ✓

Answer: Maximising value means focusing on outcomes the product produces, such as customer satisfaction and business results, rather than output measures like volume of code or backlog size.

How does releasing more frequently relate to managing risk and value, from a Product Owner perspective?

• A Release frequency has no effect on value
• B Only the Scrum Master decides release frequency
• C Frequent releases increase risk and should be avoided
• D Releasing more often shortens feedback loops, enabling earlier validation of value and faster adaptation ✓

Answer: More frequent releases shorten the feedback loop, letting the Scrum Team validate assumptions about value sooner and adapt, which is central to empirical product management.