Scrum PSPO-I Practice Test - Questions Answers, Page 13

The Developers are accountable for creating a valuable and usable Increment each Sprint. They are the people in the Scrum Team who are committed to delivering a "Done" Increment that meets the Definition of Done and the Sprint Goal. They are responsible for managing and organizing their work within the Sprint, collaborating with the Product Owner and the Scrum Master, and applying their skills and creativity to create a product that delivers value to the stakeholders and customers.

The Scrum Guide

The Developers

Understanding and Applying the Scrum Framework

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.

The Scrum Guide

Understanding and Applying the Scrum Framework

Professional Scrum Product Owner I Certification

The Sprint Retrospective is one of the five events defined by Scrum. It is a formal opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. The purpose of the Sprint Retrospective is to adapt the way of working so that it becomes more effective and enjoyable. The other options are not required by Scrum, but may be useful practices depending on the context. Developers do not have to stand up at the Daily Scrum, they can choose any format that works for them. A Sprint Burndown Chart is a common way to visualize the remaining work in a Sprint, but it is not mandated by Scrum. Release Planning is a topic that falls under the broader competency of Managing Products with Agility, but it is not a prescribed event in Scrum.

The Scrum Guide

Understanding and Applying the Scrum Framework

Professional Scrum Product Owner I Certification

The Scrum Team consists of one Scrum Master, one Product Owner, and Developers. Within a Scrum Team, there are no sub-teams or hierarchies. It is a cohesive unit of professionals focused on one objective at a time, the Product Goal. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization. The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are responsible for creating and communicating a vision, ordering the Product Backlog, and ensuring that the best possible job is done to delight customers. The Developers are the people in the Scrum Team that are committed to delivering a "Done" Increment that meets the Definition of Done and the Sprint Goal. They are responsible for managing and organizing their work within the Sprint, collaborating with the Product Owner and the Scrum Master, and applying their skills and creativity to create a product that delivers value to the stakeholders and customers. A Project Manager is not a role in the Scrum Team, as Scrum does not recognize titles for Developers, regardless of the work being performed by the person. There is no need for a Project Manager, as the Scrum Team is self-managing and accountable for delivering value.

The Scrum Guide

The Scrum Team

Professional Scrum Product Owner I Certification

According to the Scrum Guide, a Sprint can be canceled before the Sprint time-box is over. Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Developers, or the Scrum Master. A Sprint would be canceled if the Sprint Goal becomes obsolete. This might occur if the company changes direction or if market or technology conditions change. In general, a Sprint should be canceled if it no longer makes sense given the circumstances. But, due to the short duration of Sprints, cancellation rarely makes sense. Developers cannot cancel a Sprint on their own, even if they face challenges or difficulties with the selected Product Backlog items, the functional expectations, the technical dependencies, or the Product Owner's availability. Instead, they should collaborate with the Product Owner and the Scrum Master to find the best way to deliver value within the Sprint and adapt to the changing situation.

The Scrum Guide

Understanding and Applying the Scrum Framework

Professional Scrum Product Owner I Certification

The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. The Definition of Done is created by the Scrum Team, not just the Developers. The Scrum Team must have a shared understanding of what it means for work to be complete, to ensure transparency. The Definition of Done is used to assess when work is complete on the product Increment. The Definition of Done may vary significantly per Scrum Team, depending on the context. The Definition of Done evolves over time and is updated whenever the Scrum Team learns more about the product and the environment in which it operates.

The Scrum Guide

Understanding and Applying the Scrum Framework

Professional Scrum Product Owner I Certification

The Scrum Master is a servant-leader for the Scrum Team, who helps the team understand and enact Scrum values, principles, and practices1.The Scrum Master also facilitates Scrum events as requested or needed2. 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 necessary[3][3].It is a key opportunity for the Developers to plan their work for the next 24 hours and collaborate on any challenges or impediments4. The Scrum Master should coach the team on the purpose and value of the Daily Scrum, and help them find ways to make it more effective and enjoyable. The Scrum Master should also learn why the Developers want to reduce the frequency of the Daily Scrum, and work with them to address any underlying issues or concerns.The Scrum Master should not impose a decision on the team, nor delegate the decision to a vote, as these actions would undermine the self-management and empowerment of the Developers5.

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

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

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

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

The Product Owner does not make sure the Developers select enough from the Product Backlog for a Sprint.The Product Owner is responsible for maximizing the value of the product and the work of the Developers, but the Developers are self-managing and decide how much work they can do in a Sprint1.The Product Owner and the Developers collaborate on the scope of the Sprint during Sprint Planning, but the final decision is up to the Developers2. The Product Owner should not interfere with the Developers' work during the Sprint, but should provide feedback and guidance on the product value[3][3].

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

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

[3][3]:Professional Scrum Product Owner I Certification, Scrum.org, accessed on December 16, 2023

The purpose of a Sprint is to produce a valuable, useful Increment that meets the Sprint Goal and the Definition of Done1.An Increment is a concrete step toward achieving the Product Goal and is the primary measure of progress in Scrum2. The Increment must be usable and potentially releasable, meaning that it meets the quality standards set by the Scrum Team and the stakeholders[3][3].

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

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

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