Free Professional Scrum Master I Practice Questions

https://scrumguides.org/docs/scrumguide/v2020/2020-Scrum-Guide-US.pdf

Scrum is a framework for developing, delivering, and sustaining complex products. Scrum has three roles: the Product Owner, the Scrum Master, and the Developers. The Developers are the people in the Scrum Team who are committed to creating any aspect of a usable Increment in each Sprint. The Developers are not limited by titles such as programmer, designer, tester, architect, engineer, etc. The Developers are responsible for all aspects of quality, including finding and fixing bugs, tracking quality metrics, and verifying the work of other Developers. Therefore, Scrum has no “tester” role, and the Developers are responsible for quality.

Correct Answer: C and E

Short Explanation: According to the Scrum Guide 2020 1 , the product has one Product Backlog, which is the single source of work undertaken by the Scrum Team. The Product Backlog is ordered by the Product Owner, who is accountable for maximizing the value of the product resulting from the work of the Scrum Team. There should be only one Product Owner per product, who may represent the desires of a committee in the Product Backlog, but those wanting to change a Product Backlog item’s priority must address the Product Owner 1 . Having multiple Product Owners or Product Backlogs would create confusion, inconsistency, and waste in the Scrum process.

During the Sprint, the Scrum Master’s role is to facilitate inspection and adaptation opportunities as requested or needed, and to coach the team members in self-management, as stated in  3 : “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 Scrum Master is accountable for the Scrum Team’s effectiveness. They do this by enabling the Scrum Team to improve its practices, within the Scrum framework.”

According to the Scrum Guide 1 , 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 guides the Development Team in creating a “Done” Increment. The definition of “Done” is created by the development organization (or Development Team if none is available from the development organization). The definition of “Done” may vary significantly per Scrum Team, depending on the context. One aspect of Scrum Teams inspecting how they work toward their Product Goal is that they improve their definition of “Done” over time. Therefore, if a Product Backlog item worked on during the Sprint does not meet the definition of “Done”, two things that should happen with the undone Product Backlog item are:

Put it on the Product Backlog for the Product Owner to decide what to do with it, as they are accountable for effective Product Backlog management and ordering.

Do not include the item in the Increment this Sprint, as it does not meet the quality standards and may compromise value.

The other options are not appropriate, as they may compromise transparency, inspection, or adaptation.