Scrum Scrum Certifications PSPO-I Questions & Answers

• Question 131:

  True or False: Sprint Reviews are an opportunity to collect stakeholder feedback.

  A. True

  B. False

  Correct Answer: A

  The Sprint Review is an event that occurs at the end of each Sprint, where the Scrum Team and the stakeholders inspect the Increment and adapt the Product Backlog if needed. The Sprint Review is an opportunity for the Product Owner to validate that the Increment meets their expectations and delivers value to the customers and users. The Sprint Review is also an opportunity for the Developers to demonstrate their work and receive feedback from the Product Owner and the stakeholders. Stakeholders are people external to the Scrum Team who have a stake or interest in the product, such as customers, users, sponsors, managers, or other teams. Stakeholders provide valuable input, feedback, and insights to the Scrum Team regarding the product vision, goals, value proposition, requirements, features, functions, quality, usability, or market conditions. Collecting stakeholder feedback is one of the main purposes of the Sprint Review. Stakeholder feedback can help the Scrum Team to: References: Scrum Guide: https://www.scrumguides.org/scrum-guide.html Sprint Review: https://www.scrum.org/resources/what-is-a-sprint-review Stakeholders: https://www.agilealliance.org/glossary/stakeholders

• Question 132:

  Which of the following are appropriate topics for discussion during a Sprint Retrospective?

  (choose the best two answers)

  A. Identifying high priority process improvements for the next Sprint.

  B. The order of items in the Product Backlog.

  C. How the team collaborates.

  D. Documenting acceptance criteria for items in the next Sprint.

  Correct Answer: AC

  The Sprint Retrospective is an event for the Scrum Team to inspect how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done1. The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness for the next Sprint2. Therefore, appropriate topics for discussion during a Sprint Retrospective are: Identifying high priority process improvements for the next Sprint. The Scrum Team should identify the most important things that went well and the potential improvements, and create a plan for implementing some of them in the next Sprint[3] [3]. This way, the Scrum Team can continuously improve their performance and deliver more value. How the team collaborates. The Scrum Team should reflect on how they work together as a self-managing unit, and how they can enhance their skills, tools, and relationships4. This way, the Scrum Team can foster a culture of trust, respect, and collaboration. The other options are not appropriate topics for discussion during a Sprint Retrospective, as they are either related to the Product Backlog or the Sprint Backlog, which are not the focus of the Sprint Retrospective. The order of items in the Product Backlog is the responsibility of the Product Owner, who manages the Product Backlog based on the value, risk, and dependencies of the items5. The Product Owner may seek input from the Scrum Team or the stakeholders, but the final decision is up to the Product Owner. Documenting acceptance criteria for items in the next Sprint is part of the Product Backlog refinement, which is an ongoing activity throughout the Sprint, not a specific event. The Scrum Team should collaborate on refining the Product Backlog items and adding more details, such as acceptance criteria, as they become more clear and ready for selection in a Sprint Planning. References:

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

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

  4: Developing People and Teams, Scrum.org, accessed on December 16, 2023

  5: The Scrum Guide, November 2020, p. 7 The Scrum Guide, November 2020, p. 10 The Scrum Guide, November 2020, p. 10 Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023

• Question 133:

  When does a Developer become accountable for an item in the Sprint Backlog?

  (choose the best answer)

  A. During the Daily Scrum.

  B. As soon as a Developer on the Scrum Team can accommodate more work.

  C. Never. All Developers on the Scrum Team share accountability for items in the Sprint Backlog.

  D. At Sprint Planning when all of the Sprint Backlog items are split evenly across the Developers.

  Correct Answer: C

  Explanation: The Developers on the Scrum Team share accountability for the Sprint Backlog, which is a forecast of the work and the plan to deliver the Sprint Goal12. The Sprint Backlog is dynamic and can be updated by the Developers as more is learned during the Sprint34. The Developers are not individually accountable for the items in the Sprint Backlog, nor are they assigned by the Scrum Master or the Product Owner5.

• Question 134:

  You have just been hired by a company new to Scrum. Your management has assigned you to be the Scrum Master of six new Scrum Teams. These teams will build one product. Select two conditions you should strive for in this scenario.

  (choose the best two answers)

  A. Each Scrum Team should have a separate Product Backlog.

  B. There should be only one Product Owner.

  C. The product has one Product Backlog.

  D. There should be six Product Owners, one for each Scrum Team.

  E. There should be six Product Owners, reporting to a Chief Product Owner.

  Correct Answer: BC

  In Scrum, there is only one product and one Product Backlog for a given product. The Product Backlog 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 Backlog is ordered by the Product Owner based on the product vision, goals, and value.

  Having multiple Product Backlogs for one product would create confusion, duplication, inconsistency, and waste. It would also make it harder to align the Scrum Teams and the stakeholders on the same product direction and priorities.

  Therefore, each Scrum Team should not have a separate Product Backlog. 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, there should

  be only one Product Owner for one product.

  In some cases, when there are multiple Scrum Teams working on one product, it may be necessary to have some form of scaling or coordination mechanism to ensure alignment and collaboration among the teams. However, this does not

  mean that there should be multiple Product Owners or Product Backlogs. Instead, there should be ways to facilitate communication, feedback, integration, and transparency among the teams and with the Product Owner. For example, some

  frameworks or practices that can help with scaling Scrum are Nexus, LeSS, SAFe, or Scrum of Scrums.

  References:

  Scrum Guide: https://www.scrumguides.org/scrum-guide.html Nexus: https://www.scrum.org/resources/what-is-nexus LeSS: https://less.works/

  SAFe: https://www.scaledagileframework.com/

  Scrum of Scrums: https://www.agilealliance.org/glossary/scrum-of-scrums/

• Question 135:

  When must the Product Owner participate in the Daily Scrum?

  (choose the best answer)

  A. When the Scrum Master asks the Product Owner to attend.

  B. When the Product Owner is actively working on items on the Sprint Backlog; however, they participate as a Developer.

  C. When there are impediments to discuss.

  D. When the Product Owner needs to represent the stakeholders' point of view to the Developers.

  Correct Answer: B

• Question 136:

  Who must attend the Daily Scrum?

  (choose the best answer)

  A. The Scrum Master and Product Owner.

  B. The Developers and Scrum Master.

  C. The Developers.

  D. The Developers and Product Owner.

  E. The Scrum Team.

  Correct Answer: C

• Question 137:

  True or False: The Product Owner makes sure the Developers select enough from the Product

  Backlog for a Sprint to satisfy the stakeholders.

  A. True

  B. False

  Correct Answer: B

  Explanation: The Product Owner does not make sure the Developers select enough from the Product Backlog for a Sprint to satisfy the stakeholders. The Developers are the ones who determine how many Product Backlog items they select for a Sprint, based on their capacity and the Sprint Goal1. 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 is accountable for maximizing the value of the product and the work of the Developers, and for managing the Product Backlog[3][3]. The Product Owner does not have the authority to tell the Developers how much work they should do, as this would violate the principle of self-management4. References:

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

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

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

• Question 138:

  A product's success is measured by:

  (choose the best three answers)

  A. The impact on cost.

  B. The impact on my performance rating.

  C. The impact on revenue.

  D. The impact on my boss's mood.

  E. The delivery of upfront defined scope compared to the upfront planned time.

  F. The impact on customer satisfaction.

  Correct Answer: ACF

  Explanation: A product's success is measured by the value it delivers to the customers and the organization. The impact on cost, revenue, and customer satisfaction are three important indicators of value. The Scrum Guide states that "The

  Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team."1 The Product Owner should consider the cost of developing and maintaining the product, the revenue generated by the

  product, and the satisfaction of the customers and users who use the product. These factors help the Product Owner to prioritize the Product Backlog, define the Product Goal, and collaborate with the stakeholders.

  References:

  1: The Scrum Guide2, page 6

  2: The Scrum Guide

• Question 139:

  How often should Scrum Team membership change?

  (choose the best answer)

  A. Every Sprint to promote shared learning.

  B. As needed, with no special allowance for changes in productivity.

  C. Never, it reduces productivity.

  D. As needed, while taking into account a short-term reduction in productivity.

  Correct Answer: D

  The Scrum Team membership should change as needed, but not too frequently, as it may affect the team's ability to deliver value and maintain a high level of collaboration and self- organization. The Scrum Guide states that "Optimal Development Team size is small enough to remain nimble and large enough to complete significant work within a Sprint. Fewer than three Development Team members decrease interaction and results in smaller productivity gains. Having more than nine members requires too much coordination. Large Development Teams generate too much complexity for an empirical process to be useful."1 Therefore, the Scrum Team should consider the impact of changing its membership on its productivity and performance, and balance the need for stability and flexibility. References:

  1: The Scrum Guide2, page 6

  2: The Scrum Guide

• Question 140:

  Why do the Developers need a Sprint Goal?

  (choose the best answer)

  A. A Sprint Goal only gives purpose to Sprint O.

  B. Sprint Goals are not valuable. Everything is known from the Product Backlog.

  C. The Developers are more focused with a common yet specific goal.

  D. A Sprint Goal ensures that all of the Product Backlog items selected for the Sprint are implemented.

  Correct Answer: C

  Explanation: The Developers need a Sprint Goal because it gives them a common yet specific goal to focus on during the Sprint. This is because:

  The Sprint Goal is a short-term objective that provides guidance and focus to the Scrum Team throughout the Sprint. It is a flexible and negotiable commitment that can be adjusted as more is learned throughout the 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 Developers are self-managing professionals

  who organize and manage their own work. They decide how to best accomplish their work, rather than being directed by others outside the Scrum Team.

  The Developers need a Sprint Goal to align their efforts and collaborate effectively as a team. The Sprint Goal helps them prioritize and optimize their work based on value and impact. The Sprint Goal also helps them cope with uncertainty

  and complexity by providing a clear direction and a shared purpose. Other options, such as a Sprint Goal only giving purpose to Sprint 0, Sprint Goals being not valuable, or a Sprint Goal ensuring that all of the Product Backlog items selected

  for the Sprint are implemented, are not valid reasons why the Developers need a Sprint Goal. They may reflect a misunderstanding of what a Sprint Goal is or how Scrum works.

  References:

  [Scrum Guide], page 15, section "Sprint Goal"

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

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