Scrum Scrum Certifications PSPO-I Questions & Answers

• Question 41:

  Which is NOT a valid consideration when ordering a Product Backlog?

  (choose the best answer)

  A. Dependencies on other Product Backlog items.

  B. Importance to customers.

  C. Alignment with business strategy and goals.

  D. Tools and techniques.

  E. Risk.

  Correct Answer: D

  The Product Backlog is an ordered list of everything that is known to be needed in the product. It 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 Owner is accountable for ordering the Product Backlog. The Product Owner orders the items in the Product Backlog based on factors such as value, risk, priority, dependency, feedback, or market conditions. The order of the

  Product Backlog items provides a clear and consistent indication of what is most important and urgent for the product. The order of the Product Backlog items also helps the Scrum Team and the stakeholders to plan and forecast effectively.

  The tools and techniques used to create, manage, or refine the Product Backlog are not a valid consideration when ordering the Product Backlog. The tools and techniques are means to an end, not an end in themselves. The tools and

  techniques do not affect the value or quality of the product or service delivered. The tools and techniques may vary from one Product Owner to another, depending on their preferences, skills, or context. The tools and techniques may also

  change over time, as new technologies or practices emerge or evolve.

  References:

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

• Question 42:

  Developers are self-managing, which of the following do they manage?

  (choose the best answer)

  A. Product Backlog ordering.

  B. When to release, based on its progress.

  C. Sprint Backlog.

  D. Stakeholders for the Sprint Review.

  E. Sprint length.

  Correct Answer: C

  Explanation: Developers are self-managing, which means that they decide how much work they can do in a Sprint, and how they will do it1. They manage 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 create and update the Sprint Backlog throughout the Sprint as more is learned[3][3]. The other options are not managed by the Developers, but by the Product Owner or the Scrum Team as a whole. The Product Owner is accountable for ordering the Product Backlog, which is an ordered list of everything that is known to be needed in the product4. The Product Owner also decides when to release the product, based on the value, risk, and stakeholder feedback5. The Scrum Team collaborates on inviting the stakeholders for the Sprint Review, which is an event where the Scrum Team and the stakeholders inspect the product Increment and adapt the Product Backlog. The Scrum Team also decides the Sprint length, which is the time-box within which the Scrum Team delivers a product Increment. 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. 10

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

  5: Managing Products with Agility, Scrum.org, accessed on December 16, 2023 : The Scrum Guide, November 2020, p. 13 : The Scrum Guide, November 2020, p. 9

• Question 43:

  The Product Owner is the person who will be held accountable if a product does not achieve its goals or deliver value. Does this mean that the Product Owner has final say over the Definition of Done?

  (choose the best answer)

  A. Yes, the Product Owner decides the Definition of Done. The Developers may be consulted.

  B. No, the Scrum Team decides the Definition of Done, if it is not a standard of the organization. The Product Owner is just one member of the Scrum Team.

  Correct Answer: B

  Explanation: The Definition of Done is a shared understanding of what it means for work to be complete, and to ensure transparency. The Scrum Guide states that "The Developers are required to conform to the Definition of Done, as defined

  by the Scrum Team. If there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same Definition of Done."1 This means that the Product Owner does not have the final say over the

  Definition of Done, but rather collaborates with the Developers and the Scrum Master to agree on the quality standards and expectations for the product.

  References:

  1: The Scrum Guide2, page 14

  2: The Scrum Guide

• Question 44:

  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.

  Correct Answer: ABC

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

  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.

  Correct Answer: AD

  

  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.

• Question 46:

  In accordance with Scrum theory, how should a group of 100 people be divided into multiple Scrum Teams?

  (choose the best answer)

  A. Create a matrix of skills, seniority, and level of experience to assign people to teams.

  B. Check with the allocation department to see who has worked together before and make these the first teams.

  C. Understanding the product, the product vision and the rules of the Scrum framework, the people divide themselves into teams.

  D. It does not really matter since you can rotate the teams every Sprint to spread knowledge.

  Correct Answer: C

  In accordance with Scrum theory, a group of 100 people should be divided into multiple Scrum Teams by understanding the product, the product vision and the rules of the Scrum framework, and then dividing themselves into teams because:

  It respects the self-organization and empowerment of the people. The people are the ones who have the knowledge, skills, and experience to create and deliver the product. They are also the ones who will work together as Scrum Teams,

  collaborating and coordinating their efforts. Therefore, they should have the autonomy and authority to decide how to form their teams, based on their preferences, interests, and capabilities.

  It supports the alignment and coherence of the Scrum Teams. The people should have a clear and shared understanding of the product, the product vision, and the rules of the Scrum framework before forming their teams. This can help them

  to align their goals and missions, to ensure that they are working on the same product and towards the same vision. It can also help them to follow the same principles and practices of Scrum, to ensure that they are working effectively and

  consistently.

  It fosters the collaboration and synergy of the Scrum Teams. The people should form their teams in a way that maximizes their collaboration and synergy. This can mean choosing team members that complement each other's skills and

  strengths, that have good rapport and trust, that can communicate and coordinate well, and that can deliver a valuable Increment each Sprint.

  References:

  Scrum Guide 2020, page 5: "Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value in each Sprint." Scrum Guide 2020, page 5: "Scrum Teams are self-managing, meaning they internally

  decide who does what, when, and how." Scrum Guide 2020, page 9: "Multiple Scrum Teams working together on a product use one Product Backlog."

  Scrum Guide 2020, page 9: "The Product Owner is one person, not a committee."

• Question 47:

  What is the timebox for the Sprint Planning event?

  (choose the best answer)

  A. Monthly.

  B. Whenever it is done.

  C. 8 hours for a one-month Sprint.

  D. 4 hours for a one-month Sprint.

  Correct Answer: C

  The Sprint Planning is an event that occurs at the beginning of each Sprint, where the Scrum Team plans how to deliver a valuable product Increment. The Sprint Planning consists of two topics: What can be done this Sprint? and How will the chosen work get done? The outcome of the Sprint Planning is an agreed-upon Sprint Goal, a Sprint Backlog, and a plan for delivering the Increment. The timebox for the Sprint Planning event is proportional to the length of the Sprint. For a one-month Sprint, the timebox is 8 hours. For shorter Sprints, the timebox is usually shorter. The Scrum Team may decide how much time to spend on each topic within the timebox, depending on their needs and preferences. The timebox for the Sprint Planning event ensures that the Scrum Team does not spend too much or too little time on planning their work for the Sprint. The timebox also ensures that the Scrum Team has enough clarity and alignment on what and how they want to achieve during the Sprint. References: Scrum Guide: https://www.scrumguides.org/scrum-guide.html Sprint Planning: https://www.scrum.org/resources/what-is-sprint-planning

• Question 48:

  True or False: Dependencies could influence how the Product Owner orders Product Backlog items.

  A. True

  B. False

  Correct Answer: A

• Question 49:

  Who owns the Sprint Backlog?

  (choose the best answer)

  A. The Scrum Master.

  B. The Scrum Team.

  C. The Product Owner.

  D. The Developers.

  Correct Answer: D

  According to Scrum.org, the Developers own the Sprint Backlog12. The Sprint Backlog is a plan by and for the Developers1. It is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint in order to achieve the Sprint Goal1. Consequently, the Sprint Backlog is updated throughout the Sprint as more is learned1.

• Question 50:

  Scrum requires that the Product Owner must use which of the following items?

  (choose all that apply)

  A. Burndown chart.

  B. Feature burn-up.

  C. Critical Path Analysis.

  D. Project Gantt chart.

  E. None of the above.

  Correct Answer: E

  Explanation: Scrum does not require that the Product Owner must use any of the following items:

  Burndown chart: A burndown chart is a graphical representation of work left to do versus time. It can be used to track progress and forecast completion dates of projects or Sprints. However, it is not mandatory or prescribed in Scrum. It is one

  of the possible techniques that a Product Owner may use to monitor and communicate product development.

  Feature burn-up: A feature burn-up chart is a graphical representation of features completed versus time. It can be used to track progress and forecast scope changes of projects or Sprints. However, it is not mandatory or prescribed in

  Scrum. It is one of the possible techniques that a Product Owner may use to monitor and communicate product development.

  Critical Path Analysis: Critical Path Analysis is a project management technique that identifies the sequence of tasks that must be completed on time for a project or Sprint to finish on schedule. It can be used to plan, monitor, and control

  complex projects or Sprints. However, it is not mandatory or prescribed in Scrum. It is one of the possible techniques that a Product Owner may use to manage product development.

  Project Gantt chart: A project Gantt chart is a graphical representation of tasks, dependencies, durations, and milestones of a project or Sprint. It can be used to plan, monitor, and control complex projects or Sprints. However, it is not

  mandatory or prescribed in Scrum. It is one of the possible techniques that a Product Owner may use to manage product development. Therefore, the correct answer is none of the above.

  References:

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

  [Scrum Guide], page 11, section "Product Backlog" [Professional Scrum Product OwnerTM Training], page 8, section "Release Management"