Scrum Scrum Certifications PSPO-I Questions & Answers

• Question 141:

  When can Developers cancel a Sprint?

  (choose the best answer)

  A. When functional expectations are not well understood.

  B. When the selected Product Backlog items for the Sprint become unachievable.

  C. They cannot. Only Product Owners can cancel Sprints.

  D. When the Product Owner is absent too often.

  E. When a technical dependency cannot be resolved.

  Correct Answer: C

  According to the Scrum Guide, a Sprint can be canceled before the Sprint time-box is over. Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Developers, or the Scrum Master. A Sprint would be canceled if the Sprint Goal becomes obsolete. This might occur if the company changes direction or if market or technology conditions change. In general, a Sprint should be canceled if it no longer makes sense given the circumstances. But, due to the short duration of Sprints, cancellation rarely makes sense. Developers cannot cancel a Sprint on their own, even if they face challenges or difficulties with the selected Product Backlog items, the functional expectations, the technical dependencies, or the Product Owner's availability. Instead, they should collaborate with the Product Owner and the Scrum Master to find the best way to deliver value within the Sprint and adapt to the changing situation. References: The Scrum Guide Understanding and Applying the Scrum Framework Professional Scrum Product OwnerTM I Certification

• Question 142:

  Who should make sure everyone on the Scrum Team does their tasks for the Sprint?

  (choose the best answer)

  A. The Project Manager.

  B. The Product Owner.

  C. The Scrum Master.

  D. The Scrum Team.

  E. All of the above.

  Correct Answer: D

  The Scrum Team is a self-organizing and cross-functional team that delivers valuable products in an agile way. The Scrum Team consists of one Product Owner, one Scrum Master, and Developers. They are all accountable for creating a

  valuable, useful, and potentially releasable product Increment each Sprint. The Scrum Team is responsible for making sure everyone on the Scrum Team does their tasks for the Sprint. The Scrum Team does not rely on any external

  authority, manager, or leader to assign or monitor their work. The Scrum Team collaborates and coordinates their work as one unit, without any hand-offs or silos. The Scrum Team also inspects and adapts their work based on empirical

  evidence and feedback.

  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 Developers 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 Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. The Scrum Master does this by helping everyone

  understand Scrum theory and practice, both within the Scrum Team and the organization.

  The other options are not valid or relevant answers for who should make sure everyone on the Scrum Team does their tasks for the Sprint. They are either nonexistent or irrelevant roles in Scrum. They are:

  References:

  Scrum Guide: https://www.scrumguides.org/scrum-guide.html Scrum Team: https://www.scrum.org/resources/what-is-a-scrum-team Product Owner: https://www.scrum.org/resources/what-is-a-product-owner Developers: https://

  www.scrum.org/resources/what-is-a-developer-in-scrum Scrum Master: https://www.scrum.org/resources/what-is-a-scrum-master

• Question 143:

  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

  Correct Answer: B

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

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

  A. True

  B. False

  Correct Answer: B

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

  Which statement best describes the Sprint Review?

  (choose the best answer)

  A. It is a mechanism to control the Developers activities during a Sprint.

  B. It is used to congratulate the Developers if they complete their forecast or to punish the Developers if they fail to meet their forecast.

  C. It is when the Scrum Team and stakeholders inspect the outcome of a Sprint and figure out what to do next.

  D. It is a demo at the end of the Sprint for everyone in the organization to check on the work done.

  Correct Answer: C

  A sprint review is a collaborative event where the Scrum Team and stakeholders inspect the outcome of a Sprint and determine future adaptations12. It is not a mechanism to control, reward, or punish the Developers, nor is it just a demo of the work done.

• Question 146:

  During a Sprint Retrospective, the Developers propose moving the Daily Scrum to only occur on Tuesdays and Thursdays. Which two are the most appropriate responses for the Scrum Master to recommend?

  (choose the best two answers)

  A. Have the Developers vote.

  B. Acknowledge and support the self-managing team's decision.

  C. Coach the team on why the Daily Scrum is important as an opportunity to update the plan.

  D. Consider the request and decide on which days the Daily Scrum should occur.

  E. Learn why the Developers want this and work with them to improve the outcome of the Daily Scrum.

  Correct Answer: CE

  Explanation: The Scrum Master is a servant-leader for the Scrum Team, who helps the team understand and enact Scrum values, principles, and practices1. The Scrum Master also facilitates Scrum events as requested or needed2. The Daily Scrum is a 15-minute event for the Developers to inspect their progress toward the Sprint Goal and adapt the Sprint Backlog as necessary[3][3]. It is a key opportunity for the Developers to plan their work for the next 24 hours and collaborate on any challenges or impediments4. The Scrum Master should coach the team on the purpose and value of the Daily Scrum, and help them find ways to make it more effective and enjoyable. The Scrum Master should also learn why the Developers want to reduce the frequency of the Daily Scrum, and work with them to address any underlying issues or concerns. The Scrum Master should not impose a decision on the team, nor delegate the decision to a vote, as these actions would undermine the self-management and empowerment of the Developers5. References:

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

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

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

• Question 147:

  During the Sprint Retrospective a Scrum Team has identified several high priority process improvements. Which of the following statements is most accurate?

  (choose the best answer)

  A. The Scrum Team may add the items to the Sprint Backlog for the next Sprint.

  B. The Scrum Team should decline to add a process improvement to the Sprint Backlog when things are running smoothly.

  C. The Scrum Team should choose at least one high priority process improvement to place in the Product Backlog.

  D. The Scrum Master selects the most important process improvement and places it in the Sprint Backlog

  Correct Answer: A

  Explanation: The Scrum Guide states that "By the end of the Sprint Retrospective, the Scrum Team should have identified improvements that it will implement in the next Sprint. Implementing these improvements in the next Sprint is the adaptation to the inspection of the Scrum Team itself."1 This means that the Scrum Team may add the high priority process improvements to the Sprint Backlog for the next Sprint, as part of their plan to deliver the Increment and achieve the Sprint Goal. The Sprint Backlog is owned and managed by the Developers, who can update it throughout the Sprint as more is learned.1 References:

  1: The Scrum Guide2, page 16

  2: The Scrum Guide

• Question 148:

  Which statement best describes Scrum?

  (choose the best answer)

  A. A defined and predictive process that conforms to the principles of Scientific Management.

  B. A complete methodology that defines how to develop software.

  C. A framework to generate value through adaptive solutions for complex problems.

  D. A cookbook that defines best practices for software development.

  Correct Answer: C

  The best statement that describes Scrum is: A framework to generate value through adaptive solutions for complex problems. Scrum is a lightweight framework that helps people, teams, and organizations to deliver valuable products in complex and uncertain environments. Scrum is based on empiricism, which means that knowledge comes from experience and making decisions based on what is observed. Scrum employs an iterative and incremental approach to optimize predictability and control risk. Scrum is not a defined and predictive process, a complete methodology, or a cookbook that defines best practices. Scrum provides the minimal boundaries within which teams can self-organize and create innovative solutions. References: Scrum Guide, Section 1 (Definition of Scrum) and Section 2 (Uses of Scrum)

• Question 149:

  Who starts the Daily Scrum?

  (choose the best answer)

  A. The Scrum Master. This ensures that the Developers have the event, and it stays within the timebox.

  B. The person coming in last. This encourages people to be on time and helps to stay within the timebox.

  C. The Product Owner.

  D. Whoever the Developers decide should start.

  E. The person who has the token.

  Correct Answer: D

  The Daily Scrum is an event for and by the Developers. They can choose whatever structure and technique they want, as long as they focus on the progress toward the Sprint Goal and produce an actionable plan for the next day of work12. The Scrum Master, the Product Owner, and the person coming in last are not necessarily the ones who should start the Daily Scrum. The person who has the token is a possible technique, but not the only one3.

• Question 150:

  When is the Sprint Backlog created?

  (choose the best answer)

  A. Prior to Sprint Planning.

  B. During refinement.

  C. During the Sprint Retrospective.

  D. During Sprint Planning.

  Correct Answer: D

  The Sprint Backlog is created during Sprint Planning, where the Developers select the Product Backlog items that they can deliver in the Sprint and create a plan for how to do the work. The Scrum Guide states that "The Sprint Backlog is

  composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how)."1 The Sprint Backlog is owned and managed by the Developers, who can

  update it throughout the Sprint as more is learned.

  References:

  1: The Scrum Guide2, page 15

  2: The Scrum Guide