Scrum Scrum Certifications PSPO-I Questions & Answers

• Question 31:

  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.

  Correct Answer: AB

  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"

• Question 32:

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

  A. True

  B. False

  Correct Answer: B

  Explanation: 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 33:

  What typically happens if the Product Backlog is not sufficiently clear at Sprint Planning?

  (choose the best answer)

  A. The Product Owner should select the Sprint Goal for the Scrum Team so that work can begin.

  B. The Developers will find it difficult to create a Sprint forecast they are confident they can meet.

  C. Nothing in particular.

  D. The Scrum Master should not allow this to happen. Look for a new Scrum Master and re-start the Sprint.

  E. Sprint Planning is canceled so refinement can be done first.

  Correct Answer: B

  If the Product Backlog is not sufficiently clear at Sprint Planning, the Developers will find it difficult to create a Sprint forecast they are confident they can meet. 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 Product Owner is

  accountable for ensuring that the Product Backlog is transparent, visible, and understood by everyone who needs to work on it. They must collaborate with the Developers and provide clarifications, feedback, and guidance on what items are

  most important and valuable for the product. If the Product Backlog is not sufficiently clear at Sprint Planning, it means that there are items that are not well defined, ordered, or estimated. This may make it hard for the Developers to

  understand what they are supposed to build and why. It may also make it hard for them to estimate how much work they can do or how long it will take them to do it. This may result in a poor or inaccurate Sprint forecast that may affect the

  quality or value of the Increment. Other options, such as the Product Owner selecting the Sprint Goal for the Scrum Team so that work can begin, nothing in particular happening, the Scrum Master not allowing this to happen or looking for a

  new Scrum Master and re-starting the Sprint, or Sprint Planning being canceled so refinement can be done first, are not valid answers as they do not reflect what typically happens or what should happen in Scrum.

  References:

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

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

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

• Question 34:

  How much work is required of the Developers to complete a Product Backlog item selected during the Sprint Planning?

  (choose the best answer)

  A. As much as they can fit into the Sprint, with remaining work deferred to the next Sprint.

  B. As much as is required to meet the Scrum Team's Definition of Done.

  C. All development work and at least some testing.

  D. A proportional amount of time on analysis, design, development, and testing.

  Correct Answer: B

  The Developers are the people in the Scrum Team who are accountable for creating a "Done" Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality, testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand and clarify the Product Backlog items, provide feedback and estimates, and suggest improvements and innovations. The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. The Definition of Done is used to assess when work is complete on the product Increment. The amount of work required of the Developers to complete a Product Backlog item selected during the Sprint Planning depends on the Definition of Done. The Definition of Done may vary from one Scrum Team to another, depending on the context and domain of work. However, it must be consistent within one team. If there are multiple Scrum Teams working on one product, they must share a common Definition of Done. If there is an organizational standard for a Definition of Done, all Scrum Teams must follow it as a minimum. The Developers must ensure that each Product Backlog item they complete during a Sprint meets the Definition of Done. This means that they must perform all the necessary tasks and activities to deliver a high-quality product functionality that is usable, valuable, and potentially releasable. This may include analysis, design, development, testing, documentation, integration, deployment, or any other aspects that contribute to the quality and usability of the product. The other options are not valid or relevant measures for the amount of work required of the Developers to complete a Product Backlog item. They are either too vague, arbitrary, or unrealistic. They are: References: Scrum Guide: https://www.scrumguides.org/scrum-guide.html Definition of Done: https://www.scrum.org/resources/what-is-a-definition-of-done Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum

• Question 35:

  The job of a Product Owner focuses on the following:

  (choose the best two answers)

  A. Working with customers and stakeholders to identify the most valuable product requirements.

  B. Writing clear, transparent User Stories.

  C. Being with the Scrum Team all the time, just in case they need me to clarify a requirement.

  D. Clearly communicating project or release status and strategies to customers and stakeholders.

  Correct Answer: AD

  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.

  The job of a Product Owner focuses on the following aspects:

  The other options are not valid or relevant aspects of a Product Owner's job. They are either too narrow, unrealistic, 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 User Stories: https://www.agilealliance.org/glossary/user-stories

• Question 36:

  Who is on the Scrum Team?

  (choose all that apply)

  A. Scrum Master.

  B. Product Owner.

  C. Developers.

  D. Project Manager.

  E. None of the above.

  Correct Answer: ABC

  The Scrum Team consists of one Scrum Master, one Product Owner, and Developers. Within a Scrum Team, there are no sub-teams or hierarchies. It is a cohesive unit of professionals focused on one objective at a time, the Product Goal. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization. The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are responsible for creating and communicating a vision, ordering the Product Backlog, and ensuring that the best possible job is done to delight customers. The Developers are the people in the Scrum Team that are committed to delivering a "Done" Increment that meets the Definition of Done and the Sprint Goal. They are responsible for managing and organizing their work within the Sprint, collaborating with the Product Owner and the Scrum Master, and applying their skills and creativity to create a product that delivers value to the stakeholders and customers. A Project Manager is not a role in the Scrum Team, as Scrum does not recognize titles for Developers, regardless of the work being performed by the person. There is no need for a Project Manager, as the Scrum Team is self-managing and accountable for delivering value. References: The Scrum Guide The Scrum Team Professional Scrum Product OwnerTM I Certification

• Question 37:

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

  (choose the best two answers)

  A. Attending every Daily Scrum to answer questions about the Sprint Backlog items.

  B. Creating financial reporting upon the spent hours reported by the Developers.

  C. Nothing.

  D. Updating the work plan for the Developers on a daily basis.

  E. Collaborating with stakeholders, users, and customers.

  F. Working with the Scrum Team on Product Backlog refinement.

  Correct Answer: EF

  Explanation: The Product Owner is typically responsible for collaborating with stakeholders, users, and customers to understand their needs and expectations, and to validate the value of the product. The Product Owner is also responsible for

  working with the Scrum Team on Product Backlog refinement, which is the act of adding detail, estimates, and order to Product Backlog items.1 These two responsibilities help the Product Owner to maximize the value of the product and the

  work of the Developers.

  References:

  1: The Scrum Guide2, page 18

  2: The Scrum Guide

• Question 38:

  Who determines how many Product Backlog items the Developers select for a Sprint?

  (choose the best answer)

  A. The Scrum Team

  B. The Developers.

  C. The Product Owner.

  D. The Scrum Master.

  E. The stakeholders attending Sprint Planning.

  Correct Answer: B

  The Developers are the ones who determine how many Product Backlog items they select for a Sprint. The Developers are self-managing and decide how much work they can do in a Sprint1. The Product Owner and the Developers

  collaborate on the scope of the Sprint during Sprint Planning, but the final decision is up to the Developers2. The Product Owner, the Scrum Master, and the stakeholders do not have the authority to tell the Developers how many Product

  Backlog items they should select, as this would violate the principle of self-management[3][3].

  References:

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

  2: The Scrum Guide, November 2020, p. 10 [3][3]: Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023

• Question 39:

  How often should customer satisfaction be measured?

  (choose the best answer)

  A. Frequently.

  B. Quarterly.

  C. Daily.

  D. Annually.

  Correct Answer: A

  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 40:

  What enhances the transparency of an Increment?

  (choose the best answer)

  A. Keeping track of and estimating all undone work to be completed in a "hardening" Sprint.

  B. Doing all work needed to meet the Definition of Done.

  C. Reporting Sprint progress to the stakeholders daily.

  D. Updating Sprint tasks properly in the electronic tracking tool.

  Correct Answer: B

  Explanation: The Definition of Done is a shared understanding of what it means for work to be complete, and ensures transparency of the quality of the work done1. The Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints2. The Increment must be usable and potentially releasable, meaning that it meets the quality standards set by the Scrum Team and the stakeholders[3][3]. Doing all work needed to meet the Definition of Done enhances the transparency of the Increment, as it ensures that the Increment is truly done and reflects the current state of the product4. The other options do not enhance the transparency of the Increment, as they either introduce unnecessary complexity, delay, or overhead, or do not provide a clear and consistent way to measure the quality of the work done. References:

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

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

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