Free PSPO-I Exam Braindumps (page: 20)

Page 20 of 43

A Product Owner is accountable for maximizing the value of the product that is the result of the work of the Scrum Team.
Which of the following can be delegated to others, while the Product Owner remains accountable for the work?
(choose the best two answers)

  1. Attending the Sprint Retrospective.
  2. Attending the Sprint Review.
  3. Ordering Product Backlog items.
  4. Developing and communicating the Product Goal.

Answer(s): A,B

Explanation:

A Product Owner is accountable for maximizing the value of the product that is the result of the work of the Scrum Team. However, they can delegate some of their responsibilities to others, while still remaining accountable for the work. Two of the responsibilities that can be delegated to others are:
Attending the Sprint Retrospective. The Sprint Retrospective is an event where the Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. The purpose of the Sprint Retrospective is to plan ways to improve quality and effectiveness. The Product Owner may attend the Sprint Retrospective as one of the Scrum Team members who has a stake in the outcome of the product development. However, they can also choose not to attend or delegate their attendance to someone else who can represent their interests and perspectives.
Attending the Sprint Review. The Sprint Review is an event where the Scrum Team and stakeholders inspect the Increment and adapt the Product Backlog if needed. The purpose of the Sprint Review is to elicit feedback and foster collaboration. The Product Owner is accountable for ensuring that key stakeholders attend the Sprint Review and that they understand what has been done and what can be done next. However, they can also delegate some of their tasks to others who can facilitate or present the Increment on their behalf.
Other options, such as ordering Product Backlog items or developing and communicating the Product Goal, are not responsibilities that can be delegated to others by the Product Owner. They are essential accountabilities that only the Product Owner can perform.


Reference:

[Scrum Guide], page 6, section "Product Owner"
[Scrum Guide], page 18, section "Sprint Retrospective" [Scrum Guide], page 17, section "Sprint Review"
[Scrum Guide], page 11, section "Product Backlog"
[Scrum Guide], page 10, section "Product Goal"



True or False: The Product Owner must write all of the Product Backlog items (e.g., user stories, requirements, etc.) on the Product Backlog before handing them over to the Scrum Team.

  1. True
  2. False

Answer(s): B

Explanation:

It is not true that the Product Owner must write all of the Product Backlog items (e.g. user stories, requirements, etc.) on the Product Backlog before handing them over to the Scrum Team. 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 is also accountable for managing the Product Backlog items effectively. They must ensure that they are transparent, visible, and understood by everyone who needs to work on them. They must also collaborate with the Developers and stakeholders to refine, order, and prioritize them based on value and impact.
The Product Owner does not need to write all of the Product Backlog items by themselves or before handing them over to the Scrum Team. They can involve others in creating or contributing to them, such as customers, users, stakeholders, or Developers. They can also add or modify them at any time during the product development process, as long as they are clear and ready for selection in Sprint Planning.


Reference:

[Scrum Guide], page 6, section "Product Owner"
[Scrum Guide], page 11, section "Product Backlog"
[Scrum Guide], page 10, section "Product Goal"
[Scrum Guide], page 12, section "Product Backlog Refinement" [Scrum Guide], page 14, section "Sprint Planning"



What is the timebox for the Sprint Review?
(choose the best answer)

  1. 2 hours for a one-month Sprint.
  2. 1 day.
  3. 4 hours for a one-month Sprint.
  4. As long as needed.

Answer(s): C

Explanation:

The timebox for the Sprint Review is four hours for a one-month Sprint. This is because:
The Sprint Review is an event where the Scrum Team and stakeholders inspect the Increment and adapt the Product Backlog if needed. The purpose of the Sprint Review is to elicit feedback and foster collaboration.
The timebox for each Scrum event is proportional to its frequency and duration. A one-month Sprint corresponds to a maximum calendar month.
The timebox for a one-month Sprint Review is four hours. For shorter Sprints, it is usually shorter. The timebox ensures that there is enough time to inspect what has been done in relation to what could be done next and make any necessary adaptations to optimize value. Other options, such as two hours for a one-month Sprint, one day, or as long as needed, are not valid answers as they do not reflect the correct timebox for the Sprint Review.


Reference:

[Scrum Guide], page 17, section "Sprint Review"
[Scrum Guide], page 9, section "Sprint"
[Scrum Guide], page 9, section "Timeboxing Scrum Events"



True or False: The Product Owner makes sure the correct stakeholders are invited to the Sprint Retrospective. They might have important instructions for team improvements.

  1. True
  2. False

Answer(s): B

Explanation:

It is not true that the Product Owner makes sure the correct stakeholders are invited to the Sprint Retrospective. They might have important instructions for team improvements. This is because:
The Sprint Retrospective is an event where the Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. The purpose of the Sprint Retrospective is to plan ways to improve quality and effectiveness. The Sprint Retrospective is an internal event for the Scrum Team only. It is a safe and confidential space where the Scrum Team can openly and honestly reflect on their strengths and weaknesses, and identify actions to improve their performance and collaboration. The stakeholders are not invited to the Sprint Retrospective. They do not have a say in how the Scrum Team works or what they should improve. The stakeholders can provide feedback and suggestions to the Scrum Team in other events, such as the Sprint Review or the Product Backlog refinement sessions.
The Product Owner is a member of the Scrum Team who 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 does not make sure the correct stakeholders are invited to the Sprint Retrospective. They might have important instructions for team improvements. This would violate the self-management and autonomy of the Scrum Team and undermine their trust and empowerment.


Reference:

[Scrum Guide], page 18, section "Sprint Retrospective" [Scrum Guide], page 7, section "The Scrum Team"
[Scrum Guide], page 17, section "Sprint Review"
[Scrum Guide], page 6, section "Product Owner"
[Scrum Guide], page 10, section "Product Goal"



Page 20 of 43



Post your Comments and Discuss Scrum PSPO-I exam with other Community members:

Barbara commented on October 07, 2024
good content!
UNITED STATES
upvote