PSM-I Exam Dumps - Scrum Professional Scrum Master Questions and Answers

The best answers are B and C because the Scrum Master serves both the Product Owner and the Scrum Team by helping address quality concerns in a constructive, transparent, and Scrum-consistent way. Quality in Scrum is not handled outside the team or delegated only to testers. When a stakeholder raises a concern about low quality, the issue should be made visible and addressed through the Product Backlog, the Definition of Done, and direct collaboration within the Scrum Team.

Option B is correct because quality expectations and stakeholder concerns should be reflected in Product Backlog items when appropriate, and the Developers need to understand those concerns clearly. Option C is also correct because the Scrum Master helps the Product Owner find an effective way to work with the Developers and address the issue empirically.

Option A is incorrect because acceptable quality standards are not solely for Developers to decide in isolation. Option D is incorrect because Scrum does not create a separate tester role responsible for quality. Option E is too passive and delayed. A significant quality concern should be addressed promptly, not simply postponed to the Sprint Retrospective.

In the Scrum framework, there is no specific role or accountability for a Tester. Instead, the responsibility for quality lies with the entire Scrum Team, particularly the Developers. Scrum emphasizes cross-functional teams, where every team member contributes to all aspects of the development process, including testing. The Developers collectively ensure that the work meets the Definition of Done and maintains high-quality standards. This approach fosters collaboration, shared responsibility, and continuous improvement, aligning with the core principles of Scrum.

In Scrum, the Developers have the autonomy to manage their work and the Sprint Backlog. When an unexpected request comes in, even from someone as authoritative as the CEO, it should not be added directly to the Sprint Backlog without discussion.  The correct approach is for the Developers to discuss the new item with the Product Owner and the rest of the Scrum Team to understand its impact on the current Sprint Goal and to collaboratively decide the best course of action 1 2 .

This is in line with the Scrum values of  Courage ,  Focus ,  Commitment ,  Respect , and  Openness .  The team must have the courage to push back on changes that could disrupt their Sprint Goal, stay focused on their commitments, respect the agreed-upon process, and be open about the implications of introducing new work mid-Sprint 1 .

The Scrum Guide also states that once the Sprint begins, no one can force the Development Team to work on different requirements than those they forecasted for the Sprint 1 . If the CEO’s request is deemed important enough to warrant a change in the Sprint’s direction, it may lead to a negotiation of scope with the Product Owner or, in extreme cases, to the cancellation of the Sprint if the Sprint Goal becomes obsolete.  However, these are decisions that should be made collaboratively by the entire Scrum Team, not unilaterally by any single member, regardless of their position in the company

According to the Scrum Guide, two intended outcomes of the Daily Scrum are a shared understanding of the most important work to be undertaken next to achieve the best possible progress toward the Sprint goal, and new impediments for the Scrum Master to take care of. The other options are not intended outcomes of the Daily Scrum, as they are either irrelevant (such as updating a Scrum board) or inappropriate (such as providing an update or a status report).

The correct answer is C. The Scrum Team creates the Definition of Done. According to the Scrum Guide 1 , “The Developers are required to conform to the Definition of Done, which is defined and evolves with the Scrum Team.” The Definition of Done is a commitment by the Developers for the Increment, but it is also a shared understanding within the whole Scrum Team, including the Product Owner and the Scrum Master 2 . The Scrum Team collaborates to create and update the Definition of Done as needed, based on the product and organizational standards 3 . The Definition of Done is not imposed by any external authority or individual.

The correct answer is A, because the Scrum Guide states that “a Sprint can be cancelled before the Sprint time-box is over. Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Development Team, or the Scrum Master.” Therefore, a Development Team cannot cancel a Sprint by itself.

he correct answer is A, because doing all work needed to meet the definition of “Done” enhances the transparency of an increment. The Scrum Guide states that “when a Product Backlog item or an Increment is described as ‘Done’, everyone must understand what ‘Done’ means.” Therefore, by meeting the definition of “Done”, an increment becomes transparent to all stakeholders and ready for release.

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.

The correct answer is B, because the Development Team determines how work is performed during the Sprint. 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, the Development Team has the autonomy and responsibility to organize and manage its own work.

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.