PSM-I Exam Dumps - Professional Scrum Master I

According to the Scrum Guide 1 , one aspect of Scrum Teams inspecting how they work toward their Product Goal is that they create a Sprint Goal every Sprint. The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Developers on why it is building the Increment. It also provides a basis for inspecting and adapting during the Sprint Review and Sprint Retrospective. The Sprint Goal is created during the Sprint Planning event.

The correct answer is E, because all of these topics can be discussed during a Sprint Retrospective. The Scrum Guide states that “the purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. … During each Sprint Retrospective, the Scrum Team plans ways to improve product quality by adapting the definition of ‘Done’ as appropriate.” Therefore, the Scrum Team can discuss any aspect of their process, communication, skills, or definition of ‘Done’ that may help them improve.

The correct answer is A. During the Sprint, the Product Owner remains actively engaged with the Scrum Team, especially by helping clarify Product Backlog items and answering questions from the Developers about the work selected for the Sprint. This supports transparency and helps the Developers better understand the desired outcome, business context, and value of the work.

Option B is incorrect because the Sprint Backlog belongs to the Developers. They organize the work required to meet the Sprint Goal and manage the Sprint Backlog throughout the Sprint. The Product Owner does not prioritize the Developers’ tasks inside the Sprint. Option C is incorrect because the Daily Scrum is an event for the Developers. The Product Owner does not run it. Option D is incorrect because updating management is not defined as a Product Owner accountability during the Sprint.

The Product Owner’s key accountability is maximizing product value, primarily through Product Backlog management and collaboration with the Scrum Team. During a Sprint, that often includes clarifying items, answering questions, and helping the team stay aligned on value and product direction. This makes Option A the best answer.

According to the Scrum Guide 1 , 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.

The correct answer is A because the Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. Product Backlog ordering should therefore be driven primarily by value, not by keeping every Developer busy at all times. Scrum does not optimize for utilization. It optimizes for value delivery, learning, and progress toward the Product Goal.

The Scrum Master should coach the Product Owner to keep the Product Backlog ordered based on what delivers the most value and best supports product outcomes. External dependencies may influence sequencing, but they should not cause the Product Owner to abandon value-based ordering just to fill capacity. In Scrum, some inefficiency may temporarily occur due to uncertainty or dependency constraints, but that is not a reason to shift toward activity-based planning.

Option B is too prescriptive and assumes a specific backlog ordering response. Option C is incorrect because maximizing utilization is not the Product Owner’s responsibility and is not a Scrum objective. Scrum encourages focus on valuable Increments, not on ensuring that everyone is always fully occupied regardless of whether the work is the most important.

According to the Scrum Guide, 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 topics that are appropriate for discussion are those that relate to how the team does its work, such as team relations, Definition of Done, and processes, tools, communication, collaboration, quality, etc. The other options are not appropriate topics for discussion in a Sprint Retrospective, as they belong to other Scrum events (such as arranging the Sprint Backlog for the next Sprint in the Sprint Planning or evaluating the value of work in the Product Backlog in the Sprint Review).

According to the Scrum Guide, the Sprint Backlog may include any items that are a decomposition of the selected Product Backlog items, such as user stories, tasks, use cases, tests, or others. The Sprint Backlog is the Developers’ plan for the Sprint, and it contains all the work that they forecast they can do to achieve the Sprint Goal and create a “Done” Increment. The other options are not valid, as they are either too specific (such as user stories or tasks) or too vague (such as tests).