Scrum PSPO-I Exam Questions & Answers

Correct Answer: AD

The Developers are the people in the Scrum Team who are committed to creating any aspect of a usable Increment each Sprint. The Developers are accountable for organizing and managing their work. Only the Developers can decide how to perform the work during the Sprint1. The Developers plan the work necessary to create an Increment that meets the Definition of Done during the Sprint Planning event. This is often done by decomposing Product Backlog items into smaller work items of one day or less. How this is done is at the sole discretion of the Developers. The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal1. The Developers are responsible for creating and maintaining the Sprint Backlog1. The Developers are not accountable for selecting the Product Owner, reporting productivity, or any other activities that are not related to creating a Done Increment that meets the Sprint Goal123. References: Scrum Guide What is a Developer? Who Determines How Work Is Performed During The Sprint? [What is Sprint Planning?]

Correct Answer: CDE

Explanation: The reasons why it is important that there is only one Product Owner per product are:

It is clear who is accountable for the ultimate value of the product. 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.

It helps avoid barriers to effective communication and rapid decision-making. 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. They must also collaborate with the Developers and the stakeholders to refine, order, and prioritize the Product Backlog

items based on value and impact.

The Scrum Team always knows who determines the order of the Product Backlog. The Product Owner has the final authority to decide what items are more important and valuable for the product. They must communicate this order clearly

and consistently to the Scrum Team and the stakeholders. They must also respect and support the self-management of the Developers in choosing how best to accomplish their work.

Other options, such as the Scrum Master knowing who acts as their backup while on vacation or it would confuse the stakeholders if they had to work with more than one person, are not valid reasons why it is important that there is only one

Product Owner per product. They may reflect a misunderstanding of the roles and accountabilities of the Scrum Team or the stakeholders.

References:

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

[Scrum Guide], page 11, section "Product Backlog" [Scrum Guide], page 12, section "Product Backlog Refinement" [Scrum Guide], page 11, section "Product Backlog" [Scrum Guide], page 7, section "Developers"

Correct Answer: D

Sprint Planning is an event where the Scrum Team collaborates on the work to be performed during the Sprint1. The topics covered in Sprint Planning are:

What can be done. The Product Owner proposes how the product could increase its value and utility in the current Sprint, based on the Product Goal, the Product Backlog, and the latest market and stakeholder feedback. The Developers

assess the capacity and the technical feasibility of the work, and select the Product Backlog items that they can commit to for the Sprint. The Scrum Team crafts the Sprint Goal, which is a concise statement of the purpose and focus of the

Sprint2.

How to do it. The Developers plan how they will deliver a "Done" product Increment that meets the Sprint Goal. They create a plan for the first days of the Sprint, and decompose the selected Product Backlog items into smaller work items.

The Developers also identify any dependencies, risks, or impediments that may affect their work. The resulting plan is captured in the Sprint Backlog, which is owned and managed by the Developers[3][3]. Why to do it. The Product Owner

explains the value and the outcome of the work to be done in the Sprint, and how it aligns with the Product Goal and the stakeholder needs. The Product Owner also clarifies the acceptance criteria and the Definition of Done for the Product

Backlog items, and answers any questions from the Developers. The Scrum Team ensures that they have a common understanding of the Sprint Goal and the expected product Increment4.

References:

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

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

4: Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023