Scrum Scrum Certifications PSPO-I Questions & Answers

• Question 1:

  Which two things should the Scrum Team do during the first Sprint?

  (choose the best two answers)

  A. Make up a plan for the rest of the project.

  B. Define the major product features and a release plan architecture.

  C. Analyze, describe, and document the requirements for the subsequent Sprints.

  D. Build at least one piece of valuable functionality.

  E. Create at least one valuable, useful Increment.

  Correct Answer: DE

  the first Sprint is the same as any other Sprint, and the Scrum Team should deliver a potentially releasable Increment of "Done" product at its conclusion. This means that the team should build at least one piece of valuable functionality that meets the Definition of Done and aligns with the Sprint Goal. The other options are not things that the Scrum Team should do during the first Sprint, as they are either too detailed, too vague, or too long-term for the Scrum framework. The Scrum Team should not make up a plan for the rest of the project, as Scrum is an empirical process that adapts to changing requirements and feedback1. The Scrum Team should not define the major product features and a release plan architecture, as these are the responsibilities of the Product Owner, who should have a vision and a roadmap for the product2. The Scrum Team should not analyze, describe, and document the requirements for the subsequent Sprints, as this would violate the principle of emergent design and just-in-time planning3.

  1: The Scrum Guide | Scrum.org 2: What is a Product Owner? | Scrum.org 3: Emergent Design and Just-in-Time Planning | Scrum.org

• Question 2:

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

  (choose the best two answers)

  A. Bring all the people together and let them organize into Scrum Teams.

  B. Managers personally re-assign current subordinates to new teams.

  C. Existing teams propose how they would like to go about organizing into the new structure.

  D. Managers collaborate to assign individuals to specific teams.

  E. The Chief Product Owner determines the new team structures and assignments.

  Correct Answer: AC

• Question 3:

  What are three advantages of a Product Owner sharing a clearly defined Product Goal with the Scrum Team?

  (choose the best three answers)

  A. It helps the Developers estimate the date that the Product Backlog will be complete.

  B. It is not mandatory in Scrum. There is no real advantage.

  C. It provides a good overall direction so Sprints will feel less like isolated pieces of work.

  D. It helps the Scrum Team keep focus and they can weigh any decision against the Product Goal

  E. It is easier to inspect incremental progress at the Sprint Review.

  Correct Answer: CDE

  The advantages of a Product Owner sharing a clearly defined Product Goal with the Scrum Team are:

  It provides a good overall direction so Sprints will feel less like isolated pieces of work. The Product Goal is a long-term objective for the product that guides all the activities of the Scrum Team. It helps the Scrum Team align their efforts and

  focus on delivering value that contributes to the product vision. It helps the Scrum Team keep focus and they can weigh any decision against the Product Goal. The Product Goal serves as a filter for deciding what to work on and what not to

  work on. It helps the Scrum Team prioritize and optimize their work based on value and impact.

  It is easier to inspect incremental progress at the Sprint Review. The Sprint Review is an event where the Scrum Team and the stakeholders collaborate on the product and inspect how it meets the Product Goal. The Increment is a concrete

  and usable outcome of the Sprint that provides a measure of progress towards the Product Goal.

  Other options, such as helping the Developers estimate the date that the Product Backlog will be complete or being not mandatory in Scrum, are not valid advantages of having a Product Goal. They may reflect a misunderstanding of what a

  Product Goal is or how Scrum works.

  References:

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

  [Professional Scrum Product OwnerTM Training], page 6, section "Product Vision" [Professional Scrum Product OwnerTM Training], page 7, section "Product Backlog Management"

  [Scrum Guide], page 13, section "Sprint Review"

  [Scrum Guide], page 10, section "Increment"

• Question 4:

  Which of the following are true about the Product Owner?

  (choose the best two answers)

  A. The Product Owner is one person.

  B. The Scrum Team can have multiple Product Owners.

  C. The Product Owner can be represented by a committee or a team of people.

  D. The Product Owner is accountable for ordering the Product Backlog.

  Correct Answer: AD

  The Product Owner is one person, not a committee or a team of people. 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, the Scrum Team can not have multiple Product Owners. The Product Owner is accountable for ordering the Product Backlog. 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 orders the items in the Product Backlog based on factors such as value, risk, priority, dependency, feedback, or market conditions. References: Scrum Guide: https://www.scrumguides.org/scrum-guide.html Product Owner: https://www.scrum.org/resources/what-is-a-product-owner Product Backlog: https://www.scrum.org/resources/what-is-a-product-backlog

• Question 5:

  How much time must a Product Owner spend with the Developers?

  (choose the best answer)

  A. Enough so that the Product Owner is confident the Increment will meet the intended value.

  B. 40%, or more if the stakeholders agree.

  C. As much time as the Developers tell the Product Owner to be present.

  D. 100%

  Correct Answer: A

  The Product Owner must spend enough time with the Developers so that they are confident the Increment will meet the intended value. 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 Product Owner is

  accountable for maximizing the value of the product resulting from the work of the Scrum Team. They must inspect the Increment at the end of each Sprint and assess how it delivers value and contributes to the Product Goal.

  The Product Owner and the Developers must collaborate closely throughout the Sprint to ensure that they have a shared understanding of what they are building and why. The Product Owner must provide clarifications, feedback, and

  guidance to the Developers as needed to help them create a valuable Increment. The amount of time that the Product Owner must spend with the Developers may vary depending on the context, complexity, and uncertainty of the product

  development. However, it should be enough so that both parties are confident that the Increment will meet the intended value.

  Other options, such as 40%, as much time as the Developers tell them to be present, or 100%, are not valid answers as they imply a fixed or arbitrary amount of time that does not reflect the actual needs and dynamics of the product

  development.

  References:

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

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

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

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

• Question 6:

  What is the timebox for the Sprint Review?

  (choose the best answer)

  A. 2 hours for a one-month Sprint.

  B. 1 day.

  C. 4 hours for a one-month Sprint.

  D. As long as needed.

  Correct Answer: C

  The timebox for the Sprint Review is four hours for a one-month Sprint. This is because:

  The Sprint Review is an event where the Scrum Team and stakeholders inspect the Increment and adapt the Product Backlog if needed. The purpose of the Sprint Review is to elicit feedback and foster collaboration. The timebox for each

  Scrum event is proportional to its frequency and duration. A one-month Sprint corresponds to a maximum calendar month. The timebox for a one-month Sprint Review is four hours. For shorter Sprints, it is usually shorter.

  The timebox ensures that there is enough time to inspect what has been done in relation to what could be done next and make any necessary adaptations to optimize value.

  Other options, such as two hours for a one-month Sprint, one day, or as long as needed, are not valid answers as they do not reflect the correct timebox for the Sprint Review.

  References:

  [Scrum Guide], page 17, section "Sprint Review"

  [Scrum Guide], page 9, section "Sprint"

  [Scrum Guide], page 9, section "Timeboxing Scrum Events"

• Question 7:

  True or False: Multiple Scrum Teams working on the same product or system all select work from the same Product Backlog.

  A. True

  B. False

  Correct Answer: A

• Question 8:

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

  A. True

  B. False

  Correct Answer: A

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

  When might a Sprint be cancelled?

  (choose the best answer)

  A. When the Developers determine the product plan is infeasible.

  B. When it becomes clear that not everything will be finished by the end of the Sprint.

  C. When the sales department has an important new opportunity.

  D. When the Sprint Goal becomes obsolete.

  Correct Answer: D

  Explanation: A Sprint may be cancelled when the Sprint Goal becomes obsolete. 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 Sprint is a

  container for all other Scrum events and activities. It is a time-box of one month or less during which a "Done" Increment is created that meets the Sprint Goal. The Sprint has a consistent duration throughout a development effort and only

  changes duration between Sprints.

  A Sprint may be cancelled before it is over by the Product Owner if they determine that the Sprint Goal is no longer valid or valuable. This may happen due to various reasons, such as a significant change in the market, technology, business

  direction, or customer needs.

  A cancelled Sprint should be rare and exceptional. It implies a waste of time and resources that could have been spent on delivering value. It also disrupts the rhythm and flow of the Scrum Team and the stakeholders. When a Sprint is

  cancelled, any completed and "Done" Product Backlog items are reviewed and potentially released. Any incomplete Product Backlog items are re- estimated and put back on the Product Backlog. The Scrum Team then plans for a new Sprint.

  Other options, such as when the Developers determine the product plan is infeasible, when it becomes clear that not everything will be finished by the end of the Sprint, or when the sales department has an important new opportunity, are not

  valid reasons for cancelling a Sprint. 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 9, section "Sprint"

  [Scrum Guide], page 16, section "Cancelling a Sprint"

• Question 10:

  What activities would a Product Owner typically undertake in the period between the end of the current Sprint and the start of the next Sprint?

  (choose the best answer)

  A. There are no such activities. The next Sprint starts immediately after the current Sprint.

  B. Refine the Product Backlog.

  C. Update the project plan with stakeholders.

  D. Work with the Quality Assurance departments on the Increment of the current Sprint.

  Correct Answer: B

  Explanation: the Product Owner is responsible for refining the Product Backlog, which is an ongoing activity that can occur at any time, including between Sprints. The other options are not typical activities for the Product Owner between Sprints, as the next Sprint starts immediately after the current Sprint1, the project plan is replaced by the Product Backlog2, and the Quality Assurance is done by the Developers of the Scrum Team within the Sprint1.

  1: The Scrum Guide | Scrum.org 2: What is a Product Backlog? | Scrum.org