Scrum PSPO-I Online Practice Questions and Exam Preparation

Scrum PSPO-I Online Questions & Answers

• Question 1:

  What is a Product Owner typically responsible for during a Sprint?

  (choose the best two answers)

  A. Creating financial reporting upon the spent hours reported by the Developers.
  B. Collaborating with stakeholders, users, and customers.
  C. Updating the work plan for the Developers on a daily basis.
  D. Working with the Scrum Team on Product Backlog refinement.
  E. Nothing.
  F. Attending every Daily Scrum to answer questions about the Sprint Backlog items.
  B. Collaborating with stakeholders, users, and customers.
  D. Working with the Scrum Team on Product Backlog refinement.

  ---

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

  A Sprint is a timebox of one month or less within which a "Done" product Increment is created. A Sprint consists of the Sprint Planning, Daily Scrums, the development work, the Sprint Review, and the Sprint Retrospective. A Sprint is also a

  feedback loop that allows the Scrum Team and the stakeholders to inspect and adapt the product and the process.

  During a Sprint, a Product Owner is typically responsible for:

  The other options are not valid or relevant responsibilities of a Product Owner during a Sprint. They are either too administrative, micromanaging, or unrelated to the product value delivery. They are:

  References:

  Scrum Guide: https://www.scrumguides.org/scrum-guide.html Product Owner: https://www.scrum.org/resources/what-is-a-product-owner Sprint: https://www.scrum.org/resources/what-is-a-sprint-in-scrum Stakeholders: https://

  www.agilealliance.org/glossary/stakeholders Daily Scrum: https://www.scrum.org/resources/what-is-a-daily-scrum

• Question 2:

  What is the typical size for a Scrum Team?

  (choose the best answer)

  A. At least 7.
  B. 9.
  C. 10 or fewer.
  D. 7 plus or minus 3.
  C. 10 or fewer.

  ---

  Explanation/Reference:

  The typical size for a Scrum Team is 10 or fewer people, including the Product Owner, the Scrum Master, and the Developers. The Scrum Guide states that "The Scrum Team is small enough to remain nimble and large enough

  to complete significant work within a Sprint. Fewer than three people decrease interaction and results in smaller productivity gains. Having more than ten people requires too much coordination. Large teams generate too much complexity for

  an empirical process to be useful."1 This means that the optimal Scrum Team size is between 3 and 10 people, depending on the context and the nature of the work.

  References:

  1: The Scrum Guide2, page 6

  2: The Scrum Guide

• Question 3:

  True or False: Cross-functional teams are optimized to work on one component or layer of a system only.

  A. True
  B. False
  B. False

  ---

  Explanation/Reference:

  Cross-functional teams are not optimized to work on one component or layer of a system only. This is because:

  Cross-functional teams are teams that have all the skills and competencies needed to accomplish the work without depending on others who are not part of the team.

  Cross-functional teams are able to deliver value across the entire product, rather than focusing on a specific component or layer. They can work on any aspect of the product that is needed to achieve the Sprint Goal and the Product Goal.

  Cross-functional teams are more agile, collaborative, and creative than teams that are specialized or siloed. They can reduce dependencies, handoffs, and delays, and increase feedback, learning, and adaptation.

  References:

  [Scrum Guide], page 7, section "Developers"

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

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

• Question 4:

  As the Developers start work during the Sprint, they realize they have selected too much work to finish in the Sprint. What should they do?

  (choose the best answer)

  A. Find another Scrum Team to give the excess work to.
  B. As soon as possible in the Sprint, work with the Product Owner to remove some work or Product Backlog items.
  C. Inform the Product Owner at the Sprint Review, but prior to the demonstration.
  D. Reduce the Definition of Done and get all of the Product Backlog items done by the new definition.
  B. As soon as possible in the Sprint, work with the Product Owner to remove some work or Product Backlog items.

  ---

  Explanation/Reference:

  This is the best answer because it respects the Scrum values of openness, commitment, and focus. The Developers should be transparent about their progress and collaborate with the Product Owner to adjust the Sprint scope accordingly.

  The Product Owner is responsible for maximizing the value of the product and the work of the Developers, so he or she should be involved in any decisions that affect the Sprint Goal and the Product Backlog. References:

  Scrum Guide, page 10: "If the work turns out to be different than the Developers expected, they collaborate with the Product Owner to negotiate the scope of Sprint Backlog within the Sprint."

  Scrum Guide, page 11: "The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team."

• Question 5:

  Which metrics will help a Product Owner determine if a product is delivering value?

  (choose the best two answers)

  A. Customer satisfaction.
  B. Productivity.
  C. Velocity.
  D. Time to market.
  E. Percentage of scope implemented.
  A. Customer satisfaction.
  D. Time to market.

  ---

  Explanation/Reference:

  The metrics that will help a Product Owner determine if a product is delivering value are customer satisfaction and time to market. This is because:

  Customer satisfaction is a measure of how well the product meets the needs and expectations of the customers5. It reflects the value proposition of the product and the feedback from the users.

  Time to market is a measure of how quickly the product can be delivered to the market. It reflects the agility and responsiveness of the Scrum Team and the ability to deliver value early and often.

  Other metrics, such as productivity, velocity, and percentage of scope implemented, are not directly related to value delivery. They may indicate how efficiently or effectively the Scrum Team is working, but they do not necessarily reflect how

  valuable or desirable the product is for the customers or stakeholders.

  References:

  Professional Scrum Product OwnerTM Training, page 5, section "Product Value" Professional Scrum Product OwnerTM Training, page 6, section "Product Vision" Professional Scrum Product OwnerTM Training, page 7, section "Product

  Backlog Management"

  Professional Scrum Product OwnerTM Training, page 8, section "Release Management"

  Professional Scrum Product OwnerTM Training, page 9, section "Business Strategy"

  Professional Scrum Product OwnerTM Training, page 10, section "Stakeholders and Customers"

• Question 6:

  True or False: The Scrum Team is accountable for creating a valuable increment every Sprint.

  A. True
  B. False
  A. True

  ---

  Explanation/Reference:

  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

• Question 7:

  True or False: A Product Owner is essentially the same thing as a traditional Project Manager.

  A. True
  B. False
  B. False

  ---

  Explanation/Reference:

  A Product Owner is not the same thing as a traditional Project Manager. A Product Owner is a role in Scrum, a framework for developing, delivering, and sustaining complex products. A Project Manager is a role in traditional project

  management, a discipline for planning, executing, and controlling projects. A 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.

  A Project Manager is accountable for delivering the project within the predefined scope, time, and cost constraints. The Project Manager is responsible for defining and managing the project plan, resources, risks, issues, and dependencies.

  The Project Manager coordinates and controls the activities of the project team and the stakeholders and ensures that the project meets the quality standards and expectations.

  Some of the main differences between a Product Owner and a Project Manager are:

  

  References:

  Scrum Guide: https://www.scrumguides.org/scrum-guide.html Product Owner: https://www.scrum.org/resources/what-is-a-product-owner Project Manager: https://www.pmi.org/about/learn-about-pmi/what-is-project- management

• Question 8:

  The Product Owner is the person who will be held accountable if a product does not achieve its goals or deliver value. Does this mean that the Product Owner has final say over the Definition of Done?

  (choose the best answer)

  A. Yes, the Product Owner decides the Definition of Done. The Developers may be consulted.
  B. No, the Scrum Team decides the Definition of Done, if it is not a standard of the organization. The Product Owner is just one member of the Scrum Team.
  B. No, the Scrum Team decides the Definition of Done, if it is not a standard of the organization. The Product Owner is just one member of the Scrum Team.

  ---

  Explanation/Reference:

  The Definition of Done is a shared understanding of what it means for work to be complete, and to ensure transparency. The Scrum Guide states that "The Developers are required to conform to the Definition of Done, as defined

  by the Scrum Team. If there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same Definition of Done."1 This means that the Product Owner does not have the final say over the

  Definition of Done, but rather collaborates with the Developers and the Scrum Master to agree on the quality standards and expectations for the product.

  References:

  1: The Scrum Guide2, page 14

  2: The Scrum Guide

• Question 9:

  True or False: Product Owners must specify complete acceptance criteria for a Product

  Backlog item before the Developers can select the item in Sprint Planning.

  A. True
  B. False
  B. False

  ---

  Explanation/Reference:

  False: Product Owners do not have to specify complete acceptance criteria for a Product Backlog item before the Developers can select the item in Sprint Planning. Acceptance criteria are a set of conditions that a Product Backlog item must satisfy to be considered "Done" and acceptable for delivery. Acceptance criteria are not mandatory in Scrum, but they can help the Product Owner and the Developers to clarify the expectations and requirements of a Product Backlog item. Acceptance criteria can be added or refined by the Product Owner at any time, but they should be clear and testable before the Sprint starts. The Developers can select a Product Backlog item in Sprint Planning based on their understanding of its value, scope, and complexity, as well as their capacity and skills. They can also collaborate with the Product Owner to define or refine the acceptance criteria during Sprint Planning. References: Scrum Guide, Section 3.4 (The Product Backlog), Section 5.1 (Sprint Planning), and Section 6.4 (The Increment)

• Question 10:

  True or False: The Product Owner should have the entire Product Backlog documented in detail before the first Sprint can start?

  A. True
  B. False
  B. False

  ---

  Explanation/Reference:

  The Product Owner should not have the entire Product Backlog documented in detail before the first Sprint can start. 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 collaborates with the Developers and the stakeholders to refine the Product Backlog as needed to ensure that there are enough items that are sufficiently clear and ready for selection in Sprint Planning.

  The amount of detail and precision required for each Product Backlog item depends on its order, size, and complexity.

  The Product Owner does not need to have the entire Product Backlog documented in detail before the first Sprint can start, as this would imply a fixed and upfront plan that does not allow for feedback, learning, and adaptation. Instead, the

  Product Owner only needs to have enough items that are well understood and valuable for the Scrum Team to start working on them in the first Sprint.

  References:

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

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

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