Scrum PSPO-I Online Practice Questions and Exam Preparation

Scrum PSPO-I Online Questions & Answers

• Question 71:

  Which of the following are true about the Product Owner?

  (choose the best two answers)

  A. The Product Owner is one person.
  B. The Scrum Team can have multiple Product Owners.
  C. The Product Owner can be represented by a committee or a team of people.
  D. The Product Owner is accountable for ordering the Product Backlog.
  A. The Product Owner is one person.
  D. The Product Owner is accountable for ordering the Product Backlog.

  ---

  Explanation/Reference:

  The Product Owner is one person, not a committee or a team of people. The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is responsible 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. Having multiple Product Owners for one product would create conflicts, overlaps, gaps, and inefficiencies. It would also make it harder to maintain a clear and consistent product vision, strategy, roadmap, and backlog. Therefore, the Scrum Team can not have multiple Product Owners. The Product Owner is accountable for ordering the Product Backlog. 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 orders the items in the Product Backlog based on factors such as value, risk, priority, dependency, feedback, or market conditions. References: Scrum Guide: https://www.scrumguides.org/scrum-guide.html Product Owner: https://www.scrum.org/resources/what-is-a-product-owner Product Backlog: https://www.scrum.org/resources/what-is-a-product-backlog

• Question 72:

  Why would you expect a Product Owner to care that the Scrum Team adheres to its Definition of Done?

  (choose the best two answers)

  A. The Product Owner should not concern themselves with meeting the Definition of Done, it is the Developer's responsibility.
  B. To be able to punish the team when they do not meet their velocity goal for the Sprint.
  C. To forecast the team's productivity over time.
  D. The Definition of Done can affect the product's total cost of ownership.
  E. To have complete transparency into what has been done at the end of each Sprint.
  C. To forecast the team's productivity over time.
  D. The Definition of Done can affect the product's total cost of ownership.

  ---

  Explanation/Reference:

  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."

• Question 73:

  True or False: Multiple Scrum Teams working on the same product must have the same Sprint start date.

  A. True
  B. False
  B. False

  ---

  Explanation/Reference:

  Multiple Scrum Teams working on the same product do not have to have the same Sprint start date. The Scrum Guide does not prescribe any synchronization of Sprints across multiple teams1. However, it is recommended that the teams

  align their Sprint cadence and duration, and coordinate their dependencies and integration through a shared Product Backlog, a common Definition of Done, and frequent communication2. This way, the teams can deliver a coherent and

  valuable product Increment every Sprint[3][3].

  References:

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

  2: Managing Products with Agility, Scrum.org, accessed on December 16, 2023 [3][3]: Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023

• Question 74:

  The IT manager asks a Scrum Team for a status report describing the progress throughout the Sprint. The Scrum Team asks the Scrum Master for advice. The Scrum Master should:

  (choose the best answer)

  A. Tell the Developers to fit the report into the Sprint Backlog.
  B. Ask the Product Owner to send the manager the report.
  C. Create and deliver the report to the manager herself.
  D. Tell the Scrum Team to figure it out themselves.
  E. Talk to the IT manager and explain that progress in Scrum comes from inspecting an Increment at the Sprint Review.
  E. Talk to the IT manager and explain that progress in Scrum comes from inspecting an Increment at the Sprint Review.

  ---

  Explanation/Reference:

  The Scrum Master should talk to the IT manager and explain that progress in Scrum comes from inspecting an Increment at the Sprint Review. This is because:

  The Scrum Team is self-managing and does not need to report to anyone outside the team1.

  The Sprint Review is an event where the Scrum Team and the stakeholders collaborate on the product and inspect the Increment2. The Increment is a concrete and usable outcome of the Sprint that provides a measure of progress and value

  delivery3.

  The IT manager can attend the Sprint Review as a stakeholder and provide feedback on the product and the process4.

  References:

  Scrum Guide, page 7, section "The Scrum Team"

  Scrum Guide, page 13, section "Sprint Review"

  Scrum Guide, page 10, section "Increment"

  Scrum Guide, page 14, section "Sprint Review"

• Question 75:

  How often should customer satisfaction be measured?

  (choose the best answer)

  A. Frequently.
  B. Quarterly.
  C. Daily.
  D. Annually.
  A. Frequently.

  ---

  Explanation/Reference:

  Customer satisfaction is a measure of how well a product or service meets or exceeds the expectations and needs of the customers. It is an important indicator of the value and quality of a product or service, and it can affect the loyalty,

  retention, and profitability of the customers.

  Customer satisfaction should be measured frequently, as it can change over time depending on various factors, such as the market conditions, the customer feedback, the product updates, the competitor actions, and the customer behavior.

  Measuring customer satisfaction frequently can help the Product Owner and the Scrum Team to inspect and adapt their product vision, strategy, roadmap, backlog, and increments based on the customer needs and preferences. It can also

  help them to identify and resolve any issues or gaps that may affect the customer satisfaction and value delivery.

  Measuring customer satisfaction quarterly, daily, or annually is not optimal, as it may not reflect the current state of the customer satisfaction and may miss some opportunities or risks that may arise in between the measurement intervals.

  Quarterly measurement may be too slow to respond to the fast-changing market and customer demands. Daily measurement may be too noisy and costly to collect and analyze. Annual measurement may be too outdated and irrelevant to

  inform the product decisions.

  References:

  Scrum Guide: https://www.scrumguides.org/scrum-guide.html Customer Satisfaction: https://www.agilealliance.org/glossary/customer- satisfaction/

• Question 76:

  You are the Scrum Master of a new, to be developed Product. Development is going to require 45 people. What is a good first question for you to suggest the group thinks about when forming into teams?

  (choose the best answer)

  A. What is the right mixture of senior and junior people on each team?
  B. Who are the subject matter experts on each team?
  C. Who are going to be the team leads?
  D. How will we make sure all teams have the right amount of expertise?
  D. How will we make sure all teams have the right amount of expertise?

  ---

  Explanation/Reference:

  When forming a Scrum team, it is important to ensure that the team has all the skills and knowledge necessary to deliver a working product12. The Scrum team should be cross-functional and self-managing, without relying on external experts or team leads34. Therefore, the question of how to make sure all teams have the right amount of expertise is a good first question to consider when forming into teams.

• Question 77:

  Who is accountable for creating a valuable and usable Increment each Sprint?

  (choose the best answer)

  A. The Developers.
  B. The Scrum Team.
  C. The Scrum Master.
  D. The Product Owner.
  E. The CEO.
  B. The Scrum Team.

  ---

  Explanation/Reference:

  

  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.

• Question 78:

  Who determines how work is performed during the Sprint?

  (choose the best answer)

  A. The Scrum Master.
  B. The Scrum Team.
  C. Team manager.
  D. The Developers
  E. Subject matter experts.
  D. The Developers

  ---

  Explanation/Reference:

  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 Developers2. The Developers also inspect their progress toward the Sprint Goal and adapt their plan during the Daily Scrum1. The Developers are self-managing, which means they decide internally who does what, when, and how1. The Scrum Master, the Product Owner, the team manager, and the subject matter experts are not involved in determining how the work is performed during the Sprint. They may provide guidance, feedback, or support, but they do not interfere with the Developers' autonomy and accountability134. References: Scrum Guide

  What is a Developer?

  Who Determines How Work Is Performed During The Sprint? What is Sprint Planning?

• Question 79:

  Which statement best describes a Product Owner's responsibility? (choose the best answer)

  A. Ensuring that the work meets the commitments to the stakeholders.
  B. Maximizing the value of the work the Scrum Team does.
  C. Keep stakeholders from distracting the Developers.
  D. Directing the Developers.
  B. Maximizing the value of the work the Scrum Team does.

  ---

  Explanation/Reference:

  The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is responsible for creating and communicating a vision, ordering the Product Backlog,

  and ensuring that the best possible job is done to delight customers. The Product Owner does not manage the Developers, but collaborates with them and the Scrum Master to optimize the value delivery. The Product Owner does not ensure

  that the work meets the commitments to the stakeholders, but rather that the work delivers value to the stakeholders. The Product Owner does not keep stakeholders from distracting the Developers, but rather engages them and manages

  their expectations.

  References:

  Professional Scrum Product OwnerTM I Certification [The Scrum Guide]

  [The Product Owner]

• Question 80:

  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)

  A. Attending the Sprint Retrospective.
  B. Attending the Sprint Review.
  C. Ordering Product Backlog items.
  D. Developing and communicating the Product Goal.
  A. Attending the Sprint Retrospective.
  B. Attending the Sprint Review.

  ---

  Explanation/Reference:

  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.

  References:

  [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"