PSPO-I Exam Questions Tutorials

Sprint Planning is an event where the Scrum Team collaborates on the work to be performed during the Sprint1. The topics covered in Sprint Planning are:

What can be done. The Product Owner proposes how the product could increase its value and utility in the current Sprint, based on the Product Goal, the Product Backlog, and the latest market and stakeholder feedback. The Developers assess the capacity and the technical feasibility of the work, and select the Product Backlog items that they can commit to for the Sprint. The Scrum Team crafts the Sprint Goal, which is a concise statement of the purpose and focus of the Sprint2.

How to do it. The Developers plan how they will deliver a “Done” product Increment that meets the Sprint Goal. They create a plan for the first days of the Sprint, and decompose the selected Product Backlog items into smaller work items. The Developers also identify any dependencies, risks, or impediments that may affect their work. The resulting plan is captured in the Sprint Backlog, which is owned and managed by the Developers[3][3].

Why to do it. The Product Owner explains the value and the outcome of the work to be done in the Sprint, and how it aligns with the Product Goal and the stakeholder needs. The Product Owner also clarifies the acceptance criteria and the Definition of Done for the Product Backlog items, and answers any questions from the Developers. The Scrum Team ensures that they have a common understanding of the Sprint Goal and the expected product Increment4.

References:

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

2: The Scrum Guide, November 2020, p. 10

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

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

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 Owner™ I Certification

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

 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”