Scrum PSPO-I Online Practice Questions and Exam Preparation

Scrum PSPO-I Online Questions & Answers

• Question 91:

  Which two ways of creating Scrum Teams are consistent with Scrum's values?

  (choose the best two answers)

  A. Managers personally re-assign current subordinates to new teams.
  B. The Chief Product Owner determines the new team structures and assignments.
  C. Managers collaborate to assign individuals to specific teams.
  D. Existing teams propose how they would like to go about organizing into the new structure.
  E. Bring all the people together and let them organize into Scrum Teams.
  D. Existing teams propose how they would like to go about organizing into the new structure.
  E. Bring all the people together and let them organize into Scrum Teams.

  ---

  Explanation/Reference:

  The Scrum values are commitment, focus, openness, respect, and courage1. These values are embodied by the Scrum Team, which is a self-managing unit that organizes its own work and delivers a valuable product2. The Scrum Team consists of one Scrum Master, one Product Owner, and Developers[3][3]. The best way to create Scrum Teams is to respect the self-management and empowerment of the people who will do the work, and let them decide how to organize themselves into Scrum Teams. This can be done by bringing all the people together and letting them form Scrum Teams based on their skills, interests, and alignment with the product vision4. Alternatively, existing teams can propose how they would like to reorganize themselves into Scrum Teams, based on their feedback and experience5. These ways of creating Scrum Teams are consistent with the Scrum values, as they foster commitment, focus, openness, respect, and courage among the team members and stakeholders. The other options are not consistent with the Scrum values, as they involve managers or the Chief Product Owner imposing their decisions on the team members, which undermines their self-management and empowerment, and creates a lack of trust and collaboration. References:

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

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

  4: Managing Products with Agility, Scrum.org, accessed on December 16, 2023

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

• Question 92:

  When does the second Sprint start?

  (choose the best answer)

  A. After the customer completes acceptance testing of the first Sprint.
  B. Once the architectural changes for the second Sprint are approved by the senior architect.
  C. Immediately after the first Sprint.
  D. After the Product Backlog items for the second Sprint have been selected.
  C. Immediately after the first Sprint.

  ---

  Explanation/Reference:

  Sprints are fixed-length events of one month or less that serve as a container for the other Scrum events and activities. Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint. There is no gap or downtime between Sprints. The second Sprint starts right after the first Sprint, regardless of the customer acceptance testing, the architectural changes, or the Product Backlog items. References: The Scrum Guide Understanding and Applying the Scrum Framework Professional Scrum Product OwnerTM I Certification

• Question 93:

  True or False: An Increment must be released to customers or users at the end of each Sprint.

  A. True
  B. False
  B. False

  ---

  Explanation/Reference:

  An Increment is a concrete stepping stone toward the product vision. It is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints. At the end of a Sprint, the new Increment must be "Done", which means it meets the Definition of Done and is usable. The Scrum Team decides when and how to release an Increment to customers or users. The Product Owner is responsible for maximizing the value of the product and the work of the Developers, and may decide to release an Increment at any time during or after a Sprint. The Developers are responsible for creating a potentially releasable Increment each Sprint, and may collaborate with the Product Owner and the stakeholders to determine the best way to deliver value. Releasing an Increment to customers or users is not mandatory at the end of each Sprint. The Scrum Team may choose to release an Increment more or less frequently, depending on the product goals, market conditions, customer feedback, or technical feasibility. However, releasing an Increment regularly can provide many benefits, such as: References: Scrum Guide: https://www.scrumguides.org/scrum-guide.html Increment: https://www.scrum.org/resources/what-is-an-increment Releasing Value: https://www.scrum.org/resources/blog/releasing-value

• Question 94:

  Which are appropriate topics for discussion in a Sprint Retrospective?

  (choose the best three answers)

  A. Team relations.
  B. The value of work currently represented in the Product Backlog.
  C. How the Scrum Team does its work.
  D. Definition of Done.
  E. Arranging the Sprint Backlog for the next Sprint.
  A. Team relations.
  C. How the Scrum Team does its work.
  D. Definition of Done.

  ---

  Explanation/Reference:

  Correct Answers: A, C, and D.

  The Sprint Retrospective is an event where the Scrum Team reflects on how they worked together in the last Sprint and identifies ways to improve their collaboration, processes, and quality. Therefore, appropriate topics for

  discussion in a Sprint Retrospective are:

  Team relations: The Scrum Team should discuss how they communicated, interacted, and supported each other during the Sprint. They should celebrate their successes, acknowledge their challenges, and address any conflicts or issues that

  arose. They should also share feedback, appreciation, and suggestions for improvement with each other.

  How the Scrum Team does its work: The Scrum Team should inspect the methods, tools, and practices they used to deliver the product increment. They should evaluate what worked well and what could be improved. They should also

  identify any impediments, risks, or dependencies that affected their work and how they handled them.

  Definition of Done: The Scrum Team should review their Definition of Done and check if it is still relevant, clear, and achievable. They should also assess how well they adhered to it and if they delivered a potentially releasable product

  increment that meets the quality standards. They should also consider if they need to update or adapt their Definition of Done based on new insights or feedback. The following topics are not appropriate for discussion in a Sprint

  Retrospective:

  The value of work currently represented in the Product Backlog: The value of the Product Backlog items is the responsibility of the Product Owner, who should continuously refine and order them based on stakeholder needs and feedback.

  The value of the Product Backlog items is not directly related to how the Scrum Team works together and does not affect their improvement actions for the next Sprint.

  Arranging the Sprint Backlog for the next Sprint: The Sprint Backlog is the plan for the next Sprint that is created by the Scrum Team during the Sprint Planning event. The Sprint Backlog is based on the Product Backlog items that are

  selected for the next Sprint and how the Developers intend to accomplish them. The Sprint Retrospective is not a planning event but a reflection event that focuses on the past Sprint.

  References:

  [Scrum Guide], section 3.5: "The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness."

  [Professional Scrum Product Owner], chapter 7: "The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint." What is a Sprint Retrospective? |

  Scrum.org: "During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by improving work processes or adapting the definition of "Done" if appropriate and not in conflict with product or organizational

  standards."

  The Sprint Retrospective - What It Is and Tips for Making the Most of Your Meeting:

  "The focus is on how the team worked together in the last sprint, including:

  Communication Teamwork Process Tools Systems Work environment Missing competencies Collaboration with external parties"

• Question 95:

  When does a Sprint conclude?

  (choose the best answer)

  A. When all the tasks are completed by the Developers.
  B. When the Sprint Retrospective is complete.
  C. When all Product Backlog items meet their Definition of Done.
  D. When the Product Owner decides enough has been delivered to meet the Sprint Goal.
  D. When the Product Owner decides enough has been delivered to meet the Sprint Goal.

  ---

  Explanation/Reference:

  A Sprint is a time-boxed period when a Scrum Team works to complete a set amount of work that delivers value to the customer1. A Sprint concludes when the time-box expires, regardless of whether all the tasks, Product Backlog items, or Definition of Done are completed or not23. The Product Owner has the authority to cancel a Sprint if they determine that the Sprint Goal is obsolete or the work done is no longer valuable1. Therefore, the Product Owner decides when enough has been delivered to meet the Sprint Goal, and the Sprint ends accordingly.

• Question 96:

  A Scrum Master is working with a Scrum Team that has Developers in different physical locations. The Developers meet in a variety of meeting rooms and have much to do logistically (for example: reserve meeting rooms and set up conference calls) before the Daily Scrum.

  What action should the Scrum Master take?

  (choose the best answer)

  A. Allow the Developers to self-manage and determine for themselves what to do.
  B. Ask the Developers to alternate who is responsible for meeting setup.
  C. Set up the meeting and tell the Scrum Team that is how it will be done.
  D. Inform management and ask them to solve it.
  A. Allow the Developers to self-manage and determine for themselves what to do.

  ---

  Explanation/Reference:

  The Scrum Master should allow the Developers to self-manage and determine for themselves what to do because:

  It respects the autonomy and empowerment of the Developers. The Developers are accountable for organizing and managing their own work, and they are the best people to decide how to conduct their Daily Scrum. The Scrum Master

  should not impose or dictate how the meeting should be set up or run, as that would undermine the self-organization and collaboration of the Developers. It supports the continuous improvement and adaptation of the Developers. The

  Developers are expected to inspect and adapt their process and practices, and to find ways to overcome any challenges or impediments they face. The Scrum Master should not solve the problems for them, but rather facilitate their problem-

  solving and learning abilities.

  It aligns with the role and responsibilities of the Scrum Master. The Scrum Master is responsible for promoting and supporting Scrum, and for helping everyone understand and enact Scrum theory, values, principles, and practices. The Scrum

  Master is not a manager or a leader of the Developers, but rather a servant-leader who enables them to work effectively.

  References:

  Scrum Guide 2020, page 6: "Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint." Scrum Guide 2020, page 6: "The Developers are accountable for ... organizing and

  managing their work."

  Scrum Guide 2020, page 12: "The Developers can select whatever structure and techniques they want, as long as their Daily Scrum focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work. This

  creates focus and improves self-management."

  Scrum Guide 2020, page 13: "The Daily Scrum is an internal meeting for the Developers. If others are present, the Scrum Master ensures that they do not disrupt the meeting."

  Scrum Guide 2020, page 7: "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."

• Question 97:

  Which best describes the Product Backlog?

  (choose the best answer)

  A. It is allowed to grow and change as more is learned about the product and its customers.
  B. It contains all foreseeable tasks and requirements from which the Scrum Team can develop and maintain a complete project plan.
  C. It provides just enough information to enable a Scrum Team to start the design phase of a product.
  D. It is baselined to follow change management processes.
  A. It is allowed to grow and change as more is learned about the product and its customers.

  ---

  Explanation/Reference:

  The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team. The Product Backlog is dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful. The other options are not accurate descriptions of the Product Backlog, as it does not contain all foreseeable tasks and requirements, it does not provide just enough information to start the design phase, and it is not baselined to follow change management processes23.

  1: What is a Product Backlog? | Scrum.org 2: What is a Product Backlog? | Agile Alliance

  3: Product Backlog: Definition, Examples and Techniques | Wrike Guide

• Question 98:

  True or False: The Product Owner must write all of the Product Backlog items (e.g., user stories, requirements, etc.) on the Product Backlog before handing them over to the Scrum Team.

  A. True
  B. False
  B. False

  ---

  Explanation/Reference:

  It is not true that the Product Owner must write all of the Product Backlog items (e.g. user stories, requirements, etc.) on the Product Backlog before handing them over to the Scrum Team. 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 is also accountable for managing the Product Backlog items effectively. They must ensure that they are transparent, visible, and understood by everyone who needs to work on them. They must also

  collaborate with the Developers and stakeholders to refine, order, and prioritize them based on value and impact.

  The Product Owner does not need to write all of the Product Backlog items by themselves or before handing them over to the Scrum Team. They can involve others in creating or contributing to them, such as customers, users, stakeholders,

  or Developers. They can also add or modify them at any time during the product development process, as long as they are clear and ready for selection in Sprint Planning.

  References:

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

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

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

• Question 99:

  The timebox for a Daily Scrum is?

  (choose the best answer)

  A. 4 hours.
  B. The same time of day every day.
  C. Two minutes per person.
  D. 15 minutes.
  D. 15 minutes.

  ---

  Explanation/Reference:

  The Scrum Guide states that "The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours."1 The Daily Scrum is a quick and simple planning meeting designed

  to keep everyone in the loop with how other team members are getting on. It ensures that team members are fully aligned with each other and on track to hit the Sprint Goal.

  References:

  1: The Scrum Guide2, page 11

  2: The Scrum Guide

• Question 100:

  When does the next Sprint begin?

  (choose the best answer)

  A. The Monday following the Sprint Review.
  B. Immediately after the conclusion of the previous Sprint.
  C. Immediately following the next Sprint Planning.
  D. When the Product Owner is ready.
  B. Immediately after the conclusion of the previous Sprint.