How does an organization know that a product built through Scrum is successful? (Choose the best answer)

The success of a product developed using Scrum is ultimately measured by the value it delivers to its users and the organization. The most effective way to gauge this is through an empirical process. By releasing functional product increments frequently, the organization can gather real-world data on how the product is performing against its goals. Key Performance Indicators (KPIs) focused on value—such as user engagement, customer satisfaction, revenue, or market share—provide concrete evidence of success. This data is then used to inform and adapt the Product Backlog, ensuring that future development efforts are continuously aimed at maximizing value. This cycle of releasing, measuring, and adapting is the core of agile product development.

A. Velocity is a measure of the amount of work a team completes in a Sprint; it is an output metric, not an outcome or value metric.
C. Measuring time spent versus estimates is a traditional project management metric for budget and schedule adherence, not a measure of product value or market success.
D. Stakeholder acceptance in a Sprint Review confirms the Increment meets current requirements, but it is an internal validation, not a measure of real-world user value or success.

1. Schwaber, K., & Sutherland, J. (2020). The Scrum Guide. Scrum.org. The guide defines the Sprint Review's purpose: "to inspect the outcome of the Sprint and determine future adaptations. The Product Backlog may also be adjusted to meet new opportunities." (p. 10). This supports the feedback loop described in the correct answer.

2. Scrum.org. (2020). The Evidence-Based Management Guide. This guide, which complements Scrum, states that success is measured by value. It advocates for focusing on "customer outcomes and business impacts, rather than the team’s output." It introduces Key Value Areas (KVAs) which are measured by KPIs to guide investment and adaptation. (p. 4, "What is EBM?").

3. Pichler, R. (2010). Agile Product Management with Scrum: Creating Products that Customers Love. Addison-Wesley. In Chapter 4, "Working with the Product Backlog," the author emphasizes that the backlog should be dynamic and updated based on feedback and learning from released software to steer the product toward success. This aligns with feeding KPI information back into the backlog. (Section: "The Product Backlog is a Living Artifact").