PSPO-I Exam Questions & Answers

The Scrum Team is a self-organizing and cross-functional team that delivers valuable products in an agile way. The Scrum Team consists of one Product Owner, one Scrum Master, and Developers. They are all accountable for creating a valuable, useful, and potentially releasable product Increment each Sprint.

An Increment is a concrete stepping stone toward the product vision. It is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints. At the end of a Sprint, the new Increment must be ''Done'', which means it meets the Definition of Done and is usable.

The Scrum Team is accountable for creating a valuable increment every Sprint, not just once or occasionally. This means that the Scrum Team must deliver a product functionality that provides value to the customers and users and contributes to the product goals and missions. The value of an increment can be measured by various factors, such as customer satisfaction, feedback, revenue, market share, or social impact.

The Scrum Team is also accountable for creating a valuable increment every Sprint, not just any increment. This means that the Scrum Team must deliver a product functionality that meets the quality standards and expectations of the customers and users and complies with the Definition of Done. The quality of an increment can be measured by various factors, such as usability, reliability, performance, security, or maintainability.

Scrum Guide: https://www.scrumguides.org/scrum-guide.html

Scrum Team: https://www.scrum.org/resources/what-is-a-scrum-team

Increment: https://www.scrum.org/resources/what-is-an-increment

A product's success is measured by the value it delivers to the customers and the organization. The impact on cost, revenue, and customer satisfaction are three important indicators of value. The Scrum Guide states that 'The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.'1 The Product Owner should consider the cost of developing and maintaining the product, the revenue generated by the product, and the satisfaction of the customers and users who use the product. These factors help the Product Owner to prioritize the Product Backlog, define the Product Goal, and collaborate with the stakeholders.

1: The Scrum Guide2, page 6

2: The Scrum Guide

The Product Owner orders the Product Backlog items according to various criteria, such as:

The value of Product Backlog items. The Product Owner aims to maximize the value of the product and the work of the Scrum Team. Therefore, they prioritize the items that deliver the most value to the stakeholders and the users, considering factors such as customer satisfaction, market share, revenue, social impact, etc.

The dependencies between Product Backlog items. The Product Owner tries to minimize the dependencies between items, as they may create complexity, uncertainty, and risk. Therefore, they order the items in a way that reduces or eliminates the dependencies, or resolves them as early as possible.

The dependencies to other products. The Product Owner also considers the dependencies that the product has to other products, such as platforms, frameworks, libraries, services, etc. Therefore, they order the items in a way that aligns with the availability and compatibility of those products.

Scrum Guide 2020, page 11: ''The Product Owner is accountable for effective Product Backlog management, which includes ... ordering Product Backlog items; and, ensuring that the Product Backlog is transparent, visible and understood.''

Scrum Guide 2020, page 11: ''The ordering of the items in the Product Backlog is the sole responsibility of the Product Owner. They order Product Backlog items to best achieve goals and missions.''

Scrum Guide 2020, page 11: ''Higher ordered Product Backlog items are clearer and more refined than lower ordered ones.''

The Product Owner should not have the entire Product Backlog documented in detail before the first Sprint can start. This is because:

The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is never complete and constantly changes to reflect the needs and desires of the customers, users, and stakeholders.

The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are responsible for identifying and articulating the Product Goal, which is a long-term objective for the product that guides all the activities of the Scrum Team.

The Product Owner collaborates with the Developers and the stakeholders to refine the Product Backlog as needed to ensure that there are enough items that are sufficiently clear and ready for selection in Sprint Planning. The amount of detail and precision required for each Product Backlog item depends on its order, size, and complexity.

The Product Owner does not need to have the entire Product Backlog documented in detail before the first Sprint can start, as this would imply a fixed and upfront plan that does not allow for feedback, learning, and adaptation. Instead, the Product Owner only needs to have enough items that are well understood and valuable for the Scrum Team to start working on them in the first Sprint.

[Scrum Guide], page 11, section ''Product Backlog''

[Scrum Guide], page 6, section ''Product Owner''

[Scrum Guide], page 10, section ''Product Goal''

[Scrum Guide], page 12, section ''Product Backlog Refinement''

A Product Owner should not measure product value by the increase in the team's velocity. This is because:

Velocity is a measure of how much work a Scrum Team can deliver in a Sprint. It is based on the estimation of Product Backlog items that are selected for a Sprint and completed according to the Definition of Done.

Velocity is not a measure of product value. It does not reflect how well the product meets the needs and expectations of the customers, users, and stakeholders. It does not reflect how much value or impact the product creates in terms of revenue, satisfaction, or social good.

Velocity is not a goal or a target for a Scrum Team. It is a planning tool that helps them forecast their future work based on their past performance. It is not a metric that should be used to compare or judge teams or individuals.

A Product Owner should measure product value by using indicators that are relevant, meaningful, and actionable for their product context. These may include metrics such as customer feedback, usage data, market share, return on investment, or social impact.

[Scrum Guide], page 7, section ''Developers''

[Scrum Guide], page 10, section ''Definition of Done''

[Scrum Guide], page 15, section ''Sprint Backlog''

[Professional Scrum Product Owner Training], page 5, section ''Product Value''

[Professional Scrum Product Owner Training], page 9, section ''Business Strategy''