PSPO-I Online Practice Questions and Answers

Correct Answer: CDE

The advantages of a Product Owner sharing a clearly defined Product Goal with the Scrum Team are:

It provides a good overall direction so Sprints will feel less like isolated pieces of work. The Product Goal is a long-term objective for the product that guides all the activities of the Scrum Team. It helps the Scrum Team align their efforts and

focus on delivering value that contributes to the product vision. It helps the Scrum Team keep focus and they can weigh any decision against the Product Goal. The Product Goal serves as a filter for deciding what to work on and what not to

work on. It helps the Scrum Team prioritize and optimize their work based on value and impact.

It is easier to inspect incremental progress at the Sprint Review. The Sprint Review is an event where the Scrum Team and the stakeholders collaborate on the product and inspect how it meets the Product Goal. The Increment is a concrete

and usable outcome of the Sprint that provides a measure of progress towards the Product Goal.

Other options, such as helping the Developers estimate the date that the Product Backlog will be complete or being not mandatory in Scrum, are not valid advantages of having a Product Goal. They may reflect a misunderstanding of what a

Product Goal is or how Scrum works.

References:

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

[Professional Scrum Product OwnerTM Training], page 6, section "Product Vision" [Professional Scrum Product OwnerTM Training], page 7, section "Product Backlog Management"

[Scrum Guide], page 13, section "Sprint Review"

[Scrum Guide], page 10, section "Increment"

Correct Answer: B

During the Sprint Review, the stakeholder's role is not to reorder the Product Backlog, but rather to provide feedback and suggestions on the product and the process. Therefore, the answer is false because:

The Sprint Review is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration. The stakeholders are invited to attend the Sprint Review as observers, participants,

or customers, and they can share their opinions, ideas, or requests regarding the product and its features, functionality, quality, value, etc. The ordering of the Product Backlog is the sole responsibility of the Product Owner. They order

Product Backlog items to best achieve goals and missions. The Product Owner may consider the feedback and suggestions from the stakeholders, as well as other factors such as dependencies, risks, costs, etc., when ordering the Product

Backlog. However, they are not obliged to follow or implement them. The Product Backlog is not a fixed or final list of requirements, but rather an emergent and dynamic artifact that represents all the possible changes to the product. The

Product Owner is accountable for effective Product Backlog management, which includes refining, communicating, and optimizing the Product Backlog items. The Product Owner may update the Product Backlog at any time, not only during

the Sprint Review.

References:

Scrum Guide 2020, page 11: "The ordering of the items in the Product Backlog is the sole responsibility of the Product Owner."

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 15: "The Sprint Review is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration."

Correct Answer: B

If the Product Backlog is not sufficiently clear at Sprint Planning, the Developers will find it difficult to create a Sprint forecast they are confident they can meet. This is because:

Sprint Planning is an event where the Scrum Team plans for the upcoming Sprint. The purpose of Sprint Planning is to align the entire Scrum Team around a common goal and a plan for delivering an Increment that meets that goal. The

Developers are accountable for creating a Sprint forecast, which is a selection of Product Backlog items that they intend to work on during the Sprint. The Sprint forecast should be realistic, achievable, and valuable. The Product Owner is

accountable for ensuring that the Product Backlog is transparent, visible, and understood by everyone who needs to work on it. They must collaborate with the Developers and provide clarifications, feedback, and guidance on what items are

most important and valuable for the product. If the Product Backlog is not sufficiently clear at Sprint Planning, it means that there are items that are not well defined, ordered, or estimated. This may make it hard for the Developers to

understand what they are supposed to build and why. It may also make it hard for them to estimate how much work they can do or how long it will take them to do it. This may result in a poor or inaccurate Sprint forecast that may affect the

quality or value of the Increment. Other options, such as the Product Owner selecting the Sprint Goal for the Scrum Team so that work can begin, nothing in particular happening, the Scrum Master not allowing this to happen or looking for a

new Scrum Master and re-starting the Sprint, or Sprint Planning being canceled so refinement can be done first, are not valid answers as they do not reflect what typically happens or what should happen in Scrum.

References:

[Scrum Guide], page 14, section "Sprint Planning" [Scrum Guide], page 7, section "Developers"

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

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

Correct Answer: A

The purpose of a Sprint is to produce a valuable, useful Increment that meets the Sprint Goal and the Definition of Done1. An Increment is a concrete step toward achieving the Product Goal and is the primary measure of progress in Scrum2.

The Increment must be usable and potentially releasable, meaning that it meets the quality standards set by the Scrum Team and the stakeholders[3][3].

References:

1: The Scrum Guide, November 2020, p. 9

2: The Scrum Guide, November 2020, p. 6 [3][3]: The Scrum Guide, November 2020, p. 13

Correct Answer: A

The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of truth for the Scrum Team and the stakeholders. It contains all the requirements, features, functions, enhancements, fixes,

and anything else that can deliver value to the customers and users of the product.

The Product Owner is accountable for managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner

represents the interests of everyone with a stake in the product and ensures that the Scrum Team works on the right things at the right time.

The Developers are accountable for creating a "Done" Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality,

testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand and clarify the Product Backlog items, provide feedback and estimates, and

suggest improvements and innovations.

All planned work for the Product done by the Scrum Team must originate from the Product Backlog. The Scrum Team does not work on anything that is not in the Product Backlog. The Scrum Team does not add or remove anything from the

Product Backlog without consulting with the Product Owner. The Scrum Team does not accept or implement any requests or changes that are not in the Product Backlog. The Scrum Team does not create any other artifacts or documents that

are not derived from or related to the Product Backlog.

References:

Scrum Guide: https://www.scrumguides.org/scrum-guide.html Product Backlog: https://www.scrum.org/resources/what-is-a-product-backlog Product Owner: https://www.scrum.org/resources/what-is-a-product-owner Developers: https://

www.scrum.org/resources/what-is-a-developer-in-scrum

Correct Answer: CD

Explanation: The Product Owner should care that the Scrum Team adheres to its Definition of Done because:

It helps to forecast the team's productivity over time. By having a clear and consistent Definition of Done, the Product Owner can measure the amount of work that the team can deliver in each Sprint and plan accordingly. It affects the

product's total cost of ownership. By ensuring that the work done by the team meets the quality standards and expectations of the stakeholders, the Product Owner can reduce the risk of technical debt, rework, defects, and maintenance costs

in the future.

References:

Scrum Guide 2020, page 10: "The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product."

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 14: "The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment. If a Product Backlog item does not meet the Definition of Done,

it cannot be released or even presented at the Sprint Review. Instead, it returns to the Product Backlog for future consideration."

Correct Answer: B

Scrum

According to the Scrum Guide 2020, the entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint1234. This includes the Developers, the Product Owner, and the Scrum Master4. The Developers are committed to creating any aspect of a usable Increment each Sprint12, while the Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team12. The Scrum Master fosters an environment where the Scrum Team can work effectively1.

Correct Answer: B

Explanation: When there are multiple teams working on one product, each Scrum Team should not have a separate Product Owner. This is because:

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 is the sole person responsible for managing the Product Backlog, which is an emergent, ordered list of what is needed to improve the product. They must ensure that the Product

Backlog is transparent, visible, and understood by everyone who needs to work on it.

Having multiple Product Owners for one product may lead to conflicts, inconsistencies, or confusion among the Scrum Teams and the stakeholders. It may also reduce the alignment, collaboration, and ownership of the product development.

Instead of having multiple Product Owners, it is recommended to have one Product Owner who works with representatives from each Scrum Team to ensure that they have a shared understanding of the product vision, goals, and priorities.

The Product Owner may also delegate some of the Product Backlog management tasks to these representatives, but they remain accountable for the final decisions.

References:

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

[Scrum Guide], page 11, section "Product Backlog" [Scrum Guide], page 10, section "Product Goal"

[Professional Scrum Product OwnerTM Training], page 6, section "Product Vision" [Professional Scrum Product OwnerTM Training], page 9, section "Business Strategy"

Correct Answer: A

Explanation: The Scrum Team is accountable for creating a valuable increment every Sprint. The Increment is the sum of all Product Backlog items Done during a Sprint and the value of all the previous Increments. The entire Scrum Team is accountable for creating a valuable and useful Increment every Sprint1. The Product Owner is responsible for maximizing the value of the product resulting from the work of the Scrum Team1. The Developers are responsible for creating a Done Increment that meets the Sprint Goal1. The Scrum Master is responsible for establishing Scrum as defined in the Scrum Guide and helping everyone understand Scrum theory, practices, rules, and values1. References: Scrum Guide What is an Increment and how Does it Connect with the other Elements of Scrum? The Professional Product Owner

Correct Answer: A

Explanation: The Scrum Guide states that "By the end of the Sprint Retrospective, the Scrum Team should have identified improvements that it will implement in the next Sprint. Implementing these improvements in the next Sprint is the adaptation to the inspection of the Scrum Team itself."1 This means that the Scrum Team may add the high priority process improvements to the Sprint Backlog for the next Sprint, as part of their plan to deliver the Increment and achieve the Sprint Goal. The Sprint Backlog is owned and managed by the Developers, who can update it throughout the Sprint as more is learned.1 References:

1: The Scrum Guide2, page 16

2: The Scrum Guide