Scrum Updated PSPO-I Exam Questions and Answers by eshaal

The metrics that will help a Product Owner determine if a product is delivering value are customer satisfaction and time to market. This is because:

• Customer satisfaction is a measure of how well the product meets the needs and expectations of the customers5. It reflects the value proposition of the product and the feedback from the users.
• Time to market is a measure of how quickly the product can be delivered to the market. It reflects the agility and responsiveness of the Scrum Team and the ability to deliver value early and often.

Other metrics, such as productivity, velocity, and percentage of scope implemented, are not directly related to value delivery. They may indicate how efficiently or effectively the Scrum Team is working, but they do not necessarily reflect how valuable or desirable the product is for the customers or stakeholders.

References:

• Professional Scrum Product Owner™ Training, page 5, section “Product Value”
• Professional Scrum Product Owner™ Training, page 6, section “Product Vision”
• Professional Scrum Product Owner™ Training, page 7, section “Product Backlog Management”
• Professional Scrum Product Owner™ Training, page 8, section “Release Management”
• Professional Scrum Product Owner™ Training, page 9, section “Business Strategy”
• Professional Scrum Product Owner™ Training, page 10, section “Stakeholders & Customers”

The Sprint Backlog is created during Sprint Planning, where the Developers select the Product Backlog items that they can deliver in the Sprint and create a plan for how to do the work. The Scrum Guide states that "The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how)."1 The Sprint Backlog is owned and managed by the Developers, who can update it throughout the Sprint as more is learned.

References:

• 1: The Scrum Guide2, page 15
• 2: The Scrum Guide

the Product Owner is responsible for refining the Product Backlog, which is an ongoing activity that can occur at any time, including between Sprints. The other options are not typical activities for the Product Owner between Sprints, as the next Sprint starts immediately after the current Sprint1, the project plan is replaced by the Product Backlog2, and the Quality Assurance is done by the Developers of the Scrum Team within the Sprint1.

1: The Scrum Guide | Scrum.org 2: What is a Product Backlog? | Scrum.org

Sprint 0 is a term that some organizations use to describe a phase of work before the first official Sprint, where they do some upfront planning, design, architecture, or analysis1. However, this term is not consistent with the Scrum framework, which does not prescribe any pre-Sprint activities or phases2. Scrum starts with a Product Backlog that contains at least one valuable and feasible Product Goal, and enough Product Backlog items to initiate the first Sprint[3][3]. The Product Owner is accountable for maximizing the value of the product and the work of the Developers, and for managing the Product Backlog4. The Product Owner does not have any specific accountability during Sprint 0, because Sprint 0 is not a part of Scrum.

References:

1: Sprint Zero: A Good Idea or Not?, Scrum Alliance, accessed on December 16, 2023

2: The Scrum Guide, November 2020, p. 5

[3][3]: The Scrum Guide, November 2020, p. 9

4: The Scrum Guide, November 2020, p. 6