Professional Scrum Product Owner I: PSPO-I

Correct Answer: B

Explanation: The Product Owner wants the Developers to adhere to its Definition of Done to have complete transparency into what has been done at the end of each Sprint. This is because:

The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. It is a shared understanding among the Scrum Team and the stakeholders of what "Done" means for any

Product Backlog item that is selected for a Sprint. The Developers are accountable for creating a "Done" Increment in every Sprint. They must ensure that every Product Backlog item they work on meets the Definition of Done before it is

considered complete. The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They must inspect the Increment at the end of each Sprint and assess how it delivers value and

contributes to the Product Goal.

Having a clear and consistent Definition of Done helps the Product Owner have complete transparency into what has been done at the end of each Sprint. It also helps them make informed decisions about releasing, adapting, or continuing

the product development.

Other options, such as predicting the team's productivity over time, knowing what the team will deliver over the next three Sprints, or reprimanding the team when they do not meet their velocity goal for the Sprint, are not valid reasons for

wanting the Developers to adhere to its Definition of Done. They may reflect a misunderstanding of what a Definition of Done is or how Scrum works.

References:

[Scrum Guide], page 10, section "Definition of Done" [Scrum Guide], page 7, section "Developers"

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

Correct Answer: B

The amount of the Sprint Backlog that must be defined during the Sprint Planning event is enough so the Developers can create their forecast of what work they can do. 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 Developers are also

accountable for creating a plan for how they will deliver the selected Product Backlog items as a "Done" Increment. The plan may include tasks, dependencies, risks, estimates, or other information that helps them organize and manage their

work.

The amount of the Sprint Backlog that must be defined during Sprint Planning may vary depending on the context, complexity, and uncertainty of the product development. However, it should be enough so that the Developers can create their

forecast of what work they can do and have a clear direction for the first few days of the Sprint.

Other options, such as just enough to understand design and architectural implications, the entire Sprint Backlog being identified and estimated by the end of Sprint Planning, or just enough tasks for the Scrum Master to be confident in the

Developers' understanding of the Sprint, are not valid answers as they do not reflect what must be defined during Sprint Planning or what is required for creating a Sprint forecast.

References:

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

[Scrum Guide], page 15, section "Sprint Backlog" [Scrum Guide], page 14, section "Sprint Planning"

Correct Answer: AC

These are the best answers because they ensure that security concerns are addressed in a transparent and consistent way. By adding security criteria to the Definition of Done, the Scrum Team can make sure that every Increment meets a

high standard of quality and security. By creating Product Backlog items for specific security concerns, the Scrum Team can prioritize and plan them in collaboration with the Product Owner and stakeholders.

References:

Scrum Guide, page 14: "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, page 15: "The Product Backlog is an emergent, ordered list of

what is needed to improve the product."