Download Latest PSPO-I Questions

The following are true about Scrum:

Scrum is based on empiricism and lean thinking. Empiricism is the principle of making decisions based on what is observed and experienced, rather than on theory or speculation. Lean thinking is the philosophy of eliminating waste and maximizing value in any process or system. Scrum applies these concepts by providing a framework for inspecting and adapting the product and the process, and by focusing on delivering the most valuable features to the customers and stakeholders.

Scrum is a framework for developing and sustaining complex products. A complex product is one that has unpredictable or unknown aspects that require creativity, experimentation, and adaptation to deliver. A framework is a set of minimal and essential rules and roles that provide structure and guidance, but leave room for flexibility and innovation. Scrum provides such a framework for teams to collaborate and deliver complex products iteratively and incrementally, while embracing change and feedback.

Each component of Scrum serves a specific purpose and is essential to Scrum’s success and your usage of Scrum to develop complex products. Scrum consists of three roles (Product Owner, Scrum Master, Developers), five events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective), and three artifacts (Product Backlog, Sprint Backlog, Increment). Each of these components has a clear definition, accountability, and goal that contributes to the overall effectiveness and value of Scrum. Removing or changing any of these components may cause the benefits of Scrum to be lost or diminished.

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 Definition of Done is a shared understanding of what it means for work to be complete, and to ensure transparency. The Scrum Guide states that " The Developers are required to conform to the Definition of Done, as defined by the Scrum Team. If there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same Definition of Done. " 1 This means that the Product Owner does not have the final say over the Definition of Done, but rather collaborates with the Developers and the Scrum Master to agree on the quality standards and expectations for the product.

1: The Scrum Guide2, page 14

2: The Scrum Guide

Scrum

During the Sprint Retrospective, the Scrum Team discusses how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done123.This includes methods of communication, the way the Scrum Team does Sprint Planning, skills needed to improve the Developers’ ability to deliver, and the Definition of Done123.