Scrum PSPO-I Online Practice Questions and Exam Preparation

Scrum PSPO-I Online Questions & Answers

• Question 81:

  True or False: Every Scrum Team must have a Product Owner and Scrum Master.

  A. False. A Scrum Master is only required when asked for by the Scrum Team.
  B. True. Each must be 100% dedicated to the Scrum Team.
  C. False. A Product Owner can be replaced by a subject matter expert in the Scrum Team.
  D. True. Outcomes are affected by their participation and availability.
  D. True. Outcomes are affected by their participation and availability.

  ---

  Explanation/Reference:

  The Product Owner and the Scrum Master are essential roles in the Scrum Team. They have distinct accountabilities and responsibilities that contribute to the success of the product and the team. The Product Owner is responsible for maximizing the value of the product and the work of the Developers. The Scrum Master is responsible for promoting and supporting Scrum and the Scrum Team. Both roles need to be fully engaged and available to the Scrum Team throughout the Sprint.

• Question 82:

  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.
  A. Identifying high priority process improvements for the next Sprint.
  C. How the team collaborates.

  ---

  Explanation/Reference:

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

  A Project Manager working with your Scrum Team has raised concerns about progress and money spent. What are the two best responses?

  (choose the best two answers)

  A. Promote transparency by sharing the Product Backlog and ensuring the Project Manager has access.
  B. Have a discussion with the Project Manager; share the current impediments and forecast for the Sprint.
  C. Show the Earned Value Analysis (EVA) report.
  D. Scrum does not have Project Managers so disregard their concerns.
  E. Share the last stakeholder briefing document prepared by the Product Owner.
  A. Promote transparency by sharing the Product Backlog and ensuring the Project Manager has access.
  B. Have a discussion with the Project Manager; share the current impediments and forecast for the Sprint.

  ---

  Explanation/Reference:

  The two best responses to a Project Manager who has raised concerns about progress and money spent are:

  Promote transparency by sharing the Product Backlog and ensuring the Project Manager has access. This helps communicate what is needed to improve the product, what is planned for each Sprint, and what has been done so far. It also

  helps align expectations and priorities among different stakeholders. Have a discussion with the Project Manager; share the current impediments and forecast for the Sprint. This helps address any issues or risks that may affect the delivery of

  value and the achievement of the Sprint Goal. It also helps provide feedback and adaptation based on the empirical evidence and data. Other options, such as showing the Earned Value Analysis (EVA) report, Scrum does not have Project

  Managers so disregard their concerns, or sharing the last stakeholder briefing document prepared by the Product Owner, are not the best responses as they do not reflect how to effectively collaborate and communicate with the Project

  Manager or how to apply the Scrum values and principles.

  References:

  [Scrum Guide], page 11, section "Product Backlog" [Scrum Guide], page 15, section "Sprint Backlog" [Scrum Guide], page 10, section "Increment"

  [Scrum Guide], page 5, section "Scrum Theory"

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

• Question 84:

  Who is accountable for creating a valuable and usable Increment each Sprint?

  (choose the best answer)

  A. The Developers.
  B. The CEO.
  C. The Product Owner.
  D. The Scrum Master.
  E. The Scrum Team.
  A. The Developers.

  ---

  Explanation/Reference:

  The Scrum Team member who is accountable for creating a valuable and usable Increment each Sprint is the Developers. This is because:

  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 Definition of Done is a

  formal description of the state of the Increment when it meets the quality measures required for the product. It is a shared understanding among the Scrum Team and the stakeholders of what "Done" means for any Product Backlog item that

  is selected for a Sprint. The Increment is a concrete and usable outcome of the Sprint that provides a measure of progress and value delivery. It must be in useable condition regardless of whether it will be released or not.

  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.

  Other options, such as the CEO, the Product Owner, the Scrum Master, or the Scrum Team, are not accountable for creating a valuable and usable Increment each Sprint. They may have different roles and accountabilities in Scrum, but they

  do not do the actual work of creating a "Done" Increment.

  References:

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

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

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

• Question 85:

  A Sprint Retrospective should be held:

  (choose the best answer)

  A. Only when the Scrum Team determines it needs one.
  B. At the end of the last Sprint in a project or a release.
  C. At the end of each Sprint.
  D. At the beginning of each Sprint.
  C. At the end of each Sprint.

  ---

  Explanation/Reference:

  The Sprint Retrospective is a time-boxed event for the Scrum Team to inspect how the last Sprint went and plan for improvements in the next Sprint. The Scrum Guide states that "The Sprint Retrospective concludes the Sprint. It is timeboxed to a maximum of three hours for a one-month Sprint. For shorter Sprints, the event is usually shorter."1 This means that the Sprint Retrospective should be held at the end of each Sprint, regardless of the project or release status. The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements, including to product quality and working relationships.1 References:

  1: The Scrum Guide2, page 16

  2: The Scrum Guide

• Question 86:

  True or False: The Sprint Backlog is a result of Sprint Planning, and it includes the Sprint Goal.

  A. True
  B. False
  A. True

  ---

  Explanation/Reference:

  It is true that the Sprint Backlog is a result of Sprint Planning, and it includes the Sprint Goal. 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

  Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering them as a "Done" Increment. The Sprint Backlog is owned by the Developers who use it to organize and manage their work during the Sprint.

  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 Sprint Backlog

  is created by the collaborative work of the entire Scrum Team during Sprint Planning. The Product Owner proposes how the product could increase its value and utility in the current Sprint. The Developers discuss how they can deliver a

  "Done" Increment that meets this proposal. Together, they define a Sprint Goal that summarizes why the Sprint is valuable to stakeholders. Then, they select enough Product Backlog items from the top of the ordered Product Backlog to

  satisfy the Sprint Goal. Finally, they create a plan for how they will deliver those items as a "Done" Increment.

  References:

  [Scrum Guide], page 14, section "Sprint Planning" [Scrum Guide], page 15, section "Sprint Backlog" [Scrum Guide], page 15, section "Sprint Goal"

• Question 87:

  Which of the following are criteria to order Product Backlog items?

  (choose all that apply)

  A. Value of Product Backlog items.
  B. Dependencies between Product Backlog items.
  C. Dependencies to other products.
  D. The availability of the Scrum Master.
  E. All of the above.
  A. Value of Product Backlog items.
  B. Dependencies between Product Backlog items.
  C. Dependencies to other products.

  ---

  Explanation/Reference:

  The Product Owner orders the Product Backlog items according to various criteria, such as:

  The value of Product Backlog items. The Product Owner aims to maximize the value of the product and the work of the Scrum Team. Therefore, they prioritize the items that deliver the most value to the stakeholders and the users,

  considering factors such as customer satisfaction, market share, revenue, social impact, etc. The dependencies between Product Backlog items. The Product Owner tries to minimize the dependencies between items, as they may create

  complexity, uncertainty, and risk. Therefore, they order the items in a way that reduces or eliminates the dependencies, or resolves them as early as possible. The dependencies to other products. The Product Owner also considers the

  dependencies that the product has to other products, such as platforms, frameworks, libraries, services, etc. Therefore, they order the items in a way that aligns with the availability and compatibility of those products.

  References:

  Scrum Guide 2020, page 11: "The Product Owner is accountable for effective Product Backlog management, which includes ... ordering Product Backlog items; and, ensuring that the Product Backlog is transparent, visible and understood."

  Scrum Guide 2020, page 11: "The ordering of the items in the Product Backlog is the sole responsibility of the Product Owner. They order Product Backlog items to best achieve goals and missions."

  Scrum Guide 2020, page 11: "Higher ordered Product Backlog items are clearer and more refined than lower ordered ones."

• Question 88:

  Who is accountable for tracking the remaining work toward the Sprint Goal?

  (choose the best answer)

  A. The Developers.
  B. The Project Manager.
  C. The Product Owner.
  D. The Scrum Master.
  A. The Developers.

  ---

  Explanation/Reference:

  The Developers are the ones who are accountable for tracking the remaining work toward the Sprint Goal. The Developers are self-managing and decide how much work they can do in a Sprint1. They also create and update the Sprint Backlog, which is the plan for how the Developers will achieve the Sprint Goal, and the single source of truth for the work to be done in the Sprint2. The Developers use the Daily Scrum to inspect their progress toward the Sprint Goal and adapt the Sprint Backlog as necessary[3][3]. The Product Owner, the Scrum Master, and the Project Manager (if any) do not have the accountability for tracking the remaining work toward the Sprint Goal, as this is the responsibility of the Developers. 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. 11

• Question 89:

  An organization has decided to adopt Scrum, but management wants to change the terminology to fit with terminology already used.

  What will likely happen if this is done?

  (choose the best answer)

  A. Without a new vocabulary as a reminder of the change, very little change may actually happen.
  B. The organization may not understand what has changed within Scrum and the benefits of Scrum may be lost.
  C. Management may feel less anxious.
  D. All answers apply.
  D. All answers apply.

  ---

  Explanation/Reference:

• Question 90:

  Which two things are appropriate for a Scrum Master to do, if the Scrum Team does not have the tools and environment to completely finish each selected Product Backlog item?

  (choose the best two answers)

  A. Coach the Scrum Team to improve its skills, tools and environment over time and adjust the Definition of Done accordingly.
  B. Refocus the current Sprint on establishing the Scrum Team's environment instead of delivering an Increment.
  C. Encourage the Product Owner to accept partially done Increments until the situation improves.
  D. Have the Scrum Team establish a Definition of Done that is actually possible to achieve given current circumstances.
  E. Declare the Scrum Team not ready for Scrum.
  A. Coach the Scrum Team to improve its skills, tools and environment over time and adjust the Definition of Done accordingly.
  D. Have the Scrum Team establish a Definition of Done that is actually possible to achieve given current circumstances.

  ---

  Explanation/Reference:

  

  Scrum Explore The correct answers are A and D.

  A. Coach the Scrum Team to improve its skills, tools and environment over time and adjust the Definition of Done accordingly. This is an appropriate action for a Scrum Master, as it helps the Scrum Team to overcome the impediments that prevent them from delivering a potentially releasable Increment. The Definition of Done should reflect the current reality of the Scrum Team, but also be a source of continuous improvement12. D. Have the Scrum Team establish a Definition of Done that is actually possible to achieve given current circumstances. This is also an appropriate action for a Scrum Master, as it ensures that the Scrum Team has a clear and shared understanding of what it means to complete a Product Backlog item. The Definition of Done should be realistic and achievable, but also challenging and ambitious12. B. Refocus the current Sprint on establishing the Scrum Team's environment instead of delivering an Increment. This is not an appropriate action for a Scrum Master, as it violates the purpose of the Sprint, which is to deliver a valuable product Increment that meets the Sprint Goal. The Scrum Team should not change the Sprint Goal or scope during the Sprint, unless the Product Owner decides to cancel the Sprint3. C. Encourage the Product Owner to accept partially done Increments until the situation improves. This is not an appropriate action for a Scrum Master, as it compromises the quality and value of the product. The Product Owner should only accept Increments that meet the Definition of Done and the acceptance criteria. Partially done Increments increase technical debt and risk, and reduce transparency and feedback12. E. Declare the Scrum Team not ready for Scrum. This is not an appropriate action for a Scrum Master, as it undermines the Scrum values and principles. The Scrum Master should support the Scrum Team in adopting and applying Scrum, regardless of the challenges and constraints they face. The Scrum Master should foster a culture of empiricism, self-organization, collaboration, and continuous improvement.