Pass the Scrum Professional Scrum Master PSM-I Questions and answers with Dumpstech

The best answer is B. A valuable, useful Increment that meets the Definition of Done.

According to the Scrum Guide 1 , “an Increment is a concrete stepping stone toward the Product Goal. Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. In order to provide value, the Increment must be usable.” The Scrum Guide also states that “work cannot be considered part of an Increment unless it meets the Definition of Done. The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.”

Therefore, a Scrum Team should deliver a valuable, useful Increment that meets the Definition of Done at the end of each Sprint. This ensures that the product is potentially releasable and that the stakeholders can inspect and provide feedback on it.

A, C, and D are not correct answers.

A. A single document, if that is what management asked for.

This answer does not reflect the Scrum values of commitment, focus, and respect 1 . A Scrum Team should not deliver a single document just because management asked for it, but rather deliver an Increment that provides value to the customers and users. A document may be part of an Increment, but it is not an Increment by itself.

C. Failing unit tests, to identify acceptance tests for the next Sprint.

This answer does not reflect the Scrum principle of empiricism 1 . A Scrum Team should not deliver failing unit tests, but rather deliver an Increment that is thoroughly verified and meets the quality standards. Failing unit tests indicate that the work is not done and that there are defects or errors in the product. A Scrum Team should use unit tests to ensure that the product works as expected and to identify and fix any issues before delivering the Increment.

D. An Increment of software with minor known bugs in it.

This answer does not reflect the Scrum value of openness 1 . A Scrum Team should not deliver an Increment of software with minor known bugs in it, but rather deliver an Increment that meets the Definition of Done and is free of any known defects or issues. Delivering an Increment with bugs in it can compromise the trust and satisfaction of the stakeholders and can lead to technical debt or rework in the future. A Scrum Team should strive to deliver high-quality products that meet or exceed the expectations of the customers and users.

 According to the Scrum Guide, the Sprint Review is a time for the Scrum Team and the stakeholders to inspect the product Increment and adapt the Product Backlog if needed. The Product Owner is responsible for keeping the stakeholders aware of the progress of the project and inviting them to the Sprint Review. If the Product Owner has not been doing this, or if the stakeholders have not been using the Sprint Review to inspect and evaluate progress, then they may be disappointed and angry at the seventh Sprint Review. The other options are not likely factors that led to this situation, as they are either irrelevant (such as the PMO or the development area) or incorrect (such as delaying the release).

According to the Scrum Guide, the Developers are accountable for managing the progress of work during a Sprint, as they are responsible for creating a valuable Increment that meets the Definition of Done and the Sprint Goal. The other options are not valid, as they imply that the Product Owner, the Scrum Master, or the most junior member of the team are accountable for managing the progress of work, which is not consistent with Scrum.

 According to the Scrum Guide 1 , ordering Product Backlog items is solely up to the Product Owner’s discretion. The Product Owner orders items in the Product Backlog to best achieve goals and missions. To do this, they optimize value by considering various factors such as cost and benefit, risk, dependencies, date needed, etc. The Product Owner is responsible for maximizing the value of the work the Development Team does. 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. Therefore, an appropriate action for the Scrum Master to take if the Product Owner is struggling with ordering the Product Backlog is to offer the Product Owner help in understanding that the goal of ordering the Product Backlog is to maximize value.

According to the Scrum Guide, the Product Owner does not make sure that the Developers select enough from the Product Backlog for a Sprint to satisfy the stakeholders. The Developers are responsible for selecting how much work they can do in a Sprint, based on their capacity and past performance. The Product Owner may influence them by ordering and clarifying the Product Backlog items, but does not control their selection.

According to the Scrum Guide 1 , the Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of requirements for any changes to be made to the product. The Product Owner is accountable for maximizing value resulting from work by Developers. The Product Owner is also accountable for effective Product Backlog management, which includes:

Developing and explicitly communicating the Product Goal;

Creating and clearly communicating Product Backlog items;

Ordering Product Backlog items; and

Ensuring that the Product Backlog is transparent, visible and understood.

Therefore, the Product Owner is responsible for clearly expressing Product Backlog items.

The correct answer is C because the Daily Scrum is specifically an event for the Developers of the Scrum Team. According to the Scrum Guide, the Daily Scrum is held by the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work. This makes the Developers the only people who must attend.

The Scrum Master’s responsibility is to ensure that the event takes place and that attendees understand its purpose, but the Scrum Master is not required to attend unless they are actively helping the Developers or are also participating as part of the team’s work. The Product Owner is also not required to attend. While either the Scrum Master or Product Owner may be present, the Daily Scrum remains a Developers’ event.

Options A, B, D, and E are incorrect because they include roles that are not mandatory participants. Scrum is careful about this distinction to preserve self-management and ensure the Developers own daily planning. The Daily Scrum is not a status meeting for management or other roles. It is a focused inspection-and-adaptation event for the Developers.

The correct answer is D because Scrum Teams are self-managing. That means the Scrum Team, and especially the Developers with respect to Sprint Backlog execution, manages its own work rather than relying on a project manager, Product Owner, or Scrum Master to make sure individuals complete assigned tasks. Scrum does not operate through command-and-control task enforcement. Instead, the team collaborates to achieve the Sprint Goal and holds itself collectively accountable.

Option A is incorrect because Scrum does not define a Project Manager role responsible for directing daily task completion. Option B is incorrect because the Product Owner is accountable for maximizing value, not managing the team’s day-to-day task execution. Option C is incorrect because the Scrum Master coaches and facilitates Scrum but does not supervise or police whether each person does their tasks. Option E is incorrect because the roles listed do not all share this responsibility.

A key Scrum principle is collective accountability. The Scrum Team organizes its own work, inspects progress, and adapts as needed. Rather than focusing on whether each individual completes personal assignments, Scrum emphasizes whether the team is progressing toward the Sprint Goal and delivering a Done Increment.

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.

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 of “Done” is created by the development organization (or Development Team if none is available from the development organization). The definition guides the Development Team in creating a “Done” Increment.