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

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, two things that are appropriate for a Scrum Master to do if the Development Team doesn’t have the engineering tools and infrastructure to completely finish each selected Product Backlog item are:

Coach the Development Team to improve its skills, tools, and infrastructure over time and adjust the Definition of “Done” accordingly.

Have the Development Team establish a Definition of “Done” that is actually possible to achieve given current circumstances.

The correct answers are B and C because security is part of product quality and should be addressed within the Scrum Team’s ongoing work, not delegated away or deferred to a later phase. Option B is correct because security concerns can and should be made visible in the Product Backlog when there is specific work needed to address them. This ensures transparency and allows the team to inspect, prioritize, and act on those concerns as part of product development.

Option C is also correct because if security is necessary for an Increment to be complete and releasable, it belongs in the Definition of Done. This ensures that security expectations are consistently applied every Sprint rather than treated as optional or postponed.

Option A is incorrect because Scrum does not rely on handing responsibility to a separate department. Option D is incorrect because delaying security work undermines transparency and increases risk. Option E is incorrect because security should not be isolated into one future Sprint as a separate cleanup effort. Scrum promotes integrating quality, including security, continuously into development so each Increment is usable and meets appropriate standards.

The best answer is C. The function or purpose of management in Scrum is to present the Scrum Teams with insights and resources that help them improve. According to the article What is the Function or Purpose of Management in Scrum? , management is still critical to providing vision, securing resources, hiring talent, training teams, removing roadblocks, and continuously improving. Management also encourages collaboration and establishes Scrum Team autonomy, which are essential for Scrum’s values and principles.

A, B and D are not good answers because they imply a command-and-control approach that contradicts Scrum’s values of respect, openness, and self-organization. Management in Scrum is not supposed to micromanage, judge, or interfere with the work of the Developers, but rather support them and enable them to deliver value.

The correct answers are A and D, because a Development Team is responsible for resolving internal team conflicts and organizing the work required to meet the Sprint Goal. The Scrum Guide states that “development Teams are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality.” Therefore, a Development Team should manage its own work and resolve its own issues.

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.

The answer is A. True. The Sprint Backlog is a result of Sprint Planning, and it includes the Sprint Goal. According to the Scrum Guide, the Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how) 1 . The Sprint Goal is the single objective for the Sprint, and it provides coherence and focus for the Scrum Team 2 . The Sprint Backlog is a plan by and for the Developers, and it is updated throughout the Sprint as more is learned 2 .

The Product Owner is responsible for engaging the stakeholders, as stated in the Scrum Guide 1 : “The Product Owner is one person, not a committee. The Product Owner 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.”

The correct answer is A, because a good first question for you to suggest the group thinks about when forming into teams is how will we make sure all teams have the right amount of expertise. This question helps the group consider the cross-functionality and self-organization of the Development Teams, which are essential for delivering a potentially releasable Increment every Sprint.

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