Get PSPO-I Dumps : Verified Professional Scrum Product Owner (PSPO I) Exam

If the Scrum Team cannot complete its work by the end of the Sprint, the Sprint does not get extended. Instead, the unfinished Sprint Backlog Items go back to the Product Backlog and can be addressed in the following Sprint12. This approach allows the team to get better at estimating and reduces complexity due to the consistency of the Scrum Events2. The Scrum Team continuously learns and adapts12.

It is not true that a Product Owner must create clear and unambiguous acceptance criteria for each Product Backlog item before it may be selected in Sprint Planning. This is because:

• Acceptance criteria are a set of conditions that a Product Backlog item must satisfy to be accepted by the Product Owner or the stakeholders. They are used to verify that the item meets the expected quality and value standards.
• Acceptance criteria are not mandatory or prescribed in Scrum. They are one of the possible techniques that a Product Owner may use to communicate their expectations and requirements to the Developers and the stakeholders. They are not part of the Scrum Guide or the Definition of Done.
• Acceptance criteria do not need to be created before Sprint Planning. They can be created or refined at any time during the product development process, as long as they are clear and agreed upon before the item is considered complete. They can also be changed or updated based on feedback or new insights.
• The only requirement for a Product Backlog item to be selected in Sprint Planning is that it is sufficiently clear and ready for selection. This means that it has enough detail and precision for the Developers to understand what they are supposed to build and why. It also means that it has been refined and ordered by the Product Owner based on value and impact.

References:

• [Scrum Guide], page 14, section “Sprint Planning”
• [Scrum Guide], page 12, section “Product Backlog Refinement”
• [Professional Scrum Product Owner™ Training], page 7, section “Product Backlog Management”

According to the Scrum Guide1, the Developers are responsible for selecting the amount of work they can do in a Sprint, based on their capacity and past performance2. If they realize that the workload may be greater than their capacity, they can either remove or change some of the selected Product Backlog items, or they can start the Sprint and monitor the progress, making adjustments as needed3. Recruiting additional Developers, canceling the Sprint, or working overtime are not valid actions, as they would disrupt the Scrum values of commitment, focus, and respect

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

 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”