Free Scrum PSM-I Practice Exam with Questions & Answers | Set: 14

A Product Owner releases each Increment when it makes sense, as stated in [2]: “The Product Owner decides when to release an Increment. This can be done at any time during or after a Sprint. The Product Owner may choose to release an Increment when it delivers enough value to customers or users, when it meets a market opportunity, when it reduces risk or uncertainty, or when it aligns with other business goals.”

The correct answer is B, because the Product Owner does not make sure the team selects enough from the Product Backlog for a Sprint to satisfy the stakeholders. The Scrum Guide states that “the number of items selected from the Product Backlog for the Sprint is solely up to the Development Team. Only the Development Team can assess what it can accomplish over the upcoming Sprint.” Therefore, the Development Team is responsible for choosing the scope of work for a Sprint.

The Scrum Master should talk to the IT manager and explain that progress in Scrum comes from inspecting an Increment at the Sprint Review, as stated in [5]: “The Scrum Master should educate the IT manager about how Scrum works and how progress is measured. The Scrum Master should invite the IT manager to attend the Sprint Review where the Development Team demonstrates what was accomplished during the Sprint. The Scrum Master should also explain that status reports are not necessary in Scrum, as transparency is ensured by using artifacts such as Product Backlog, Sprint Backlog, and Increment.”

The recommended size for a Scrum Team is 10 or fewer people, as stated in the Scrum Guide: “The recommended size of a Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint, typically 10 or fewer people.”

If the Development Team cannot complete its work by the end of the Sprint, then the Sprint length holds and the Development Team continuously learns what is actually possible to do within a Sprint of this length, as stated in [7]: “If a Development Team determines it has overcommitted itself for a Sprint, one option is to collaborate with the Product Owner to negotiate removing or reducing scope. Another option is to simply work hard and do its best, without cutting quality or pressuring individuals. In either case, the Development Team learns from its experience and uses this learning when planning future Sprints.”

According to the Scrum Guide1, the purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. Inspected elements often vary with domain, practices, and people involved. The Scrum Team identifies the most helpful changes to improve its effectiveness. The most impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint. Therefore, two appropriate topics for discussion during a Sprint Retrospective are:

Identifying high priority process improvements for the next Sprint.

How the team collaborates.

The other options are not relevant or appropriate for the Sprint Retrospective.

References: Scrum Guide

The correct answer is B, because the Scrum Guide states that “at the end of a Sprint, the new Increment must be ‘Done,’ which means it must be in useable condition and meet the Scrum Team’s definition of ‘Done’. An increment is a body of inspectable, done work that supports empiricism at the end of the Sprint. The increment is a step toward a vision or goal.” Therefore, all the increments from different Scrum Teams working on the same product should be integrated every Sprint to enable inspection and adaptation by the Product Owner and stakeholders.

The correct answer is B, because the Sprint Backlog is created during the Sprint Planning meeting. The Scrum Guide states that “the Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal.”

The correct answer is A, because the role of management in Scrum is to facilitate the Scrum Teams with insights and resources that help them improve. The Scrum Guide states that “the organization respects their self-organization by not telling them how they should do their work.” Therefore, management should support the Scrum Teams by providing them with an environment that fosters collaboration, learning, and innovation.

According to the Scrum Guide1, the purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. Inspected elements often vary with domain, practices, and people involved. The Scrum Team identifies the most helpful changes to improve its effectiveness. The most impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint. The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. The Scrum Master is part of the Scrum Team and should participate as a Scrum team member and facilitate as requested or needed.

References: Scrum Guide