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

The best answer is C. When multiple Scrum Teams are working together on a product, they must mutually define and comply with the same Definition of Done. This is because the Definition of Done creates transparency and ensures that the product Increment meets the quality standards required for the product 1 . If each Scrum Team has its own Definition of Done, it may lead to inconsistencies, conflicts, and technical debt in the product. Therefore, the Scrum Teams should collaborate and agree on a common Definition of Done that applies to all Product Backlog Items and Increments. This way, the Scrum Teams can deliver a potentially releasable product Increment at the end of every Sprint 2 .

The correct answers are B and E, because Scrum has no “tester” role and everyone in the Development Team is responsible for quality. The Scrum Guide states that “the Development Team consists of professionals who do the work of delivering a potentially releasable Increment of ‘Done’ product at the end of each Sprint. Development Teams are structured and empowered by the organization to organize and manage their own work. The resulting synergy optimizes the Development Team’s overall efficiency and effectiveness.”

According to the Scrum Guide 1 , there are five values that guide decisions within Scrum teams:

Commitment

Focus

Openness

Respect

Courage

In order to achieve the benefits of Scrum, it is important to enact these values. Two actions that demonstrate the commitment of Scrum Team members are:

Help the other Scrum Team members, as they work together as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment by the end of the Sprint.

Do your best, as they strive to deliver a potentially releasable Increment that meets the definition of “Done” and provides value to the stakeholders.

According to the Scrum Guide 1 , the Developers are self-organizing and decide how to turn Product Backlog items into an Increment of value. No one tells them how to do their work. The Developers are accountable for creating a plan for the Sprint, the Sprint Backlog. The other roles are not responsible for making sure everyone on the Development Team does their tasks for the Sprint.

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.

According to the Scrum Guide, the Scrum Master is responsible for coaching the Scrum Team to improve its skills, tools and environment over time and adjust the Definition of Done accordingly 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 1 .  The Definition of Done should be possible to achieve given current circumstances 2 . Therefore, option B and E are appropriate for a Scrum Master to do, if the Scrum Team does not have the tools and environment to completely finish each selected Product Backlog item.

Option A is not appropriate because declaring the Scrum Team not ready for Scrum implies that there is a fixed set of prerequisites for using Scrum, which is not true.  Scrum is a framework that can be applied to any complex product development effort 1 .

Option C is not appropriate because encouraging the Product Owner to accept partially done Increments until the situation improves violates the principle of transparency.  Transparency requires that the Increment is a usable product that meets the current Definition of Done 1 .  Accepting partially done Increments also increases technical debt and reduces value delivery 3 .

Option D is not appropriate because refocusing the current Sprint on establishing the Scrum Team’s environment instead of delivering an Increment goes against the purpose of a Sprint. A Sprint is a time-boxed event that serves as a container for the other Scrum events and activities.  The goal of each Sprint is to deliver a potentially releasable Increment that adheres to the current Definition of Done 1 .

The correct answer is C because the Product Owner is a full member of the Scrum Team and participates in the Sprint Retrospective along with the Developers and Scrum Master. The Sprint Retrospective is not a meeting only for Developers or only for process specialists. It is an event for the Scrum Team to inspect how the last Sprint went with regard to individuals, interactions, processes, tools, and their Definition of Done, and then identify improvements for the future.

The Product Owner’s role in this event is not to act as an external observer or a stakeholder representative. Instead, the Product Owner contributes as a Scrum Team member by sharing observations, listening to concerns, and collaborating on ways to improve effectiveness and value delivery. This shared participation supports transparency and continuous improvement.

Option A is incorrect because the Retrospective is an internal Scrum Team event, not a stakeholder reporting session. Option B is incorrect because the Product Owner absolutely should participate. Option D is incorrect because capturing backlog requirements is not the purpose of the Retrospective. The main purpose is improvement of how the team works together.

The best two answers are B and D. These two ways of dealing with regulatory compliance issues are consistent with Scrum’s values and principles, as they allow the Scrum Team to deliver valuable and potentially releasable increments of the product while meeting the necessary standards and regulations. They also enable the Scrum Team to inspect and adapt their compliance strategy based on feedback and changing requirements.

A is not a good answer because it creates a separate silo of responsibility for compliance issues, which can lead to delays, conflicts, and inefficiencies. It also violates the Scrum value of transparency, as the compliance team may not have full visibility into the product development process.

C is not a good answer because it implies a waterfall approach that assumes all the compliance requirements are known and fixed upfront, which is rarely the case. It also reduces the flexibility and responsiveness of the Scrum Team, as they may have to follow a rigid plan that does not reflect the current reality of the product or the market.

The best answer is C. Ensure every Increment meets them.  Non-functional requirements (NFRs) are system qualities that guide the design of the solution and often serve as constraints across the relevant backlogs 1 .  NFRs are persistent qualities and constraints typically revisited as part of the definition of done (DoD) for each Iteration, PI, or release 1 . The Scrum Team should ensure that every Increment meets the NFRs, as they are part of the product requirements and affect the value delivery and customer satisfaction.

According to the Scrum Guide, the Product Owner is accountable for clearly expressing Product Backlog items, as he or she is responsible for managing and prioritizing the Product Backlog. The other options are not valid, as they imply that the Product Owner can be replaced by a business analyst, or that the Scrum Master or the Developers can express the Product Backlog items.