PSPO PSPO-I Exam Questions and Answers PDF

The best approach for Scrum Teams to produce valuable Increments is to be accountable for developing functionality from beginning to end, as this enables them to deliver potentially releasable products that meet the definition of “Done”. The Scrum Guide states that " The Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint. " 1 This means that the Developers are not limited by the boundaries of components, layers, or technologies, but rather they collaborate and coordinate to deliver a complete and integrated product that satisfies the Sprint Goal and the Product Owner’s expectations.

1: The Scrum Guide2, page 7

2: The Scrum Guide

The Scrum Team is a self-managing unit that organizes its own work and delivers a valuable product1. The Scrum Team consists of one Scrum Master, one Product Owner, and Developers2. The Scrum Team is accountable for creating a valuable, useful Increment every Sprint[3][3] . If a Developer is having conflicts with other team members that affect the delivery of the Increment, the Scrum Team is responsible for resolving the issue and deciding whether to remove the Developer from the team or not. The Product Owner, the Scrum Master, and the hiring manager do not have the authority to remove a Developer from the Scrum Team, as this would violate the principle of self-management4.

The Daily Scrum is a 15-minute event for the Developers to inspect their progress toward the Sprint Goal and adapt the Sprint Backlog as necessary1. It is a key opportunity for the Developers to plan their work for the next 24 hours and collaborate on any challenges or impediments2. If the frequency of the Daily Scrum were to be lowered to every two or three days, three key concerns would be:

The Sprint Backlog may become inaccurate. The Sprint Backlog is the plan for how the Developers will achieve the Sprint Goal, and it is updated throughout the Sprint as more is learned[3][3] . The Daily Scrum is a chance for the Developers to inspect the Sprint Backlog and make adjustments based on the current situation4. If the Daily Scrum is less frequent, the Sprint Backlog may not reflect the reality of the work, and the Developers may lose track of their progress and alignment with the Sprint Goal.

Opportunities to inspect and adapt the Sprint Backlog are lost. Scrum is based on empiricism, which means that knowledge comes from experience and making decisions based on what is observed5. The Daily Scrum is an essential event for the Developers to apply empiricism to their work, by inspecting the Sprint Backlog and adapting it to optimize the value and quality of the Increment. If the Daily Scrum is less frequent, the Developers may miss opportunities to inspect and adapt their work, and may not be able to deliver a valuable, useful Increment every Sprint.

Impediments are raised and resolved more slowly. An impediment is anything that prevents the Scrum Team from delivering a product Increment. The Daily Scrum is a forum for the Developers to identify and communicate any impediments that affect their work, and to seek help from the Scrum Master or other team members. If the Daily Scrum is less frequent, the impediments may not be raised and resolved in a timely manner, and may cause delays or quality issues in the product delivery.

The Product Owner wants the Developers to adhere to its Definition of Done to have complete transparency into what has been done at the end of each Sprint. This is because:

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 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.

Having a clear and consistent Definition of Done helps the Product Owner have complete transparency into what has been done at the end of each Sprint. It also helps them make informed decisions about releasing, adapting, or continuing the product development.

Other options, such as predicting the team’s productivity over time, knowing what the team will deliver over the next three Sprints, or reprimanding the team when they do not meet their velocity goal for the Sprint, are not valid reasons for wanting the Developers to adhere to its Definition of Done. They may reflect a misunderstanding of what a Definition of Done is or how Scrum works.