Scrum Professional Scrum Master I PSM-I Exam Dumps: Updated Questions & Answers (March 2026)

The correct answer is B, because a product Increment does not have to be released to production at the end of each Sprint. 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, a product Increment must be potentially releasable, but the decision to release it is up to the Product Owner.

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.

The two intended outcomes of the Daily Scrum are A and D.

A. Identification of impediments that may prevent the Developers from achieving the Sprint Goal.

The Daily Scrum is an opportunity for the Developers to inspect their progress toward the Sprint Goal and to identify any impediments or challenges that may hinder them from completing the work in the Sprint Backlog 1 . The Scrum Master can help the Developers remove these impediments or find ways to overcome them 2 .

D. A shared understanding of the most important work to be undertaken next to achieve the best possible progress toward the Sprint Goal.

The Daily Scrum is also an opportunity for the Developers to adapt their plan for the next 24 hours based on their current situation and the Sprint Goal 1 . The Developers can select whatever structure and techniques they want, as long as their Daily Scrum focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work 1 . This creates focus and improves self-management.

B, C, and E are not intended outcomes of the Daily Scrum.

B. An update of completed tasks and of the remaining work so the Scrum Master can plan the next day.

The Daily Scrum is not a status meeting or a report for the Scrum Master or anyone else 2 . The Developers are responsible for conducting and facilitating the Daily Scrum, not the Scrum Master 1 . The Scrum Master’s role is to ensure that the event happens, that it is positive and productive, and that it stays within the 15-minute timebox 2 .

C. An updated Scrum board to make Sprint progress transparent for the stakeholders.

The Daily Scrum is an internal meeting for the Scrum Team, not for external stakeholders 1 . The Scrum board is a tool that can help the Developers visualize their work, but it is not an outcome of the Daily Scrum. The outcome of the Daily Scrum should be an updated Sprint Backlog and an updated Sprint plan to achieve the Sprint Goal 3 .

E. A status report for the upper management indicating what each individual has done, will be doing, and what is impeding him/her.

The Daily Scrum is not a status report for anyone, especially not for upper management 2 . The purpose of the Daily Scrum is to inspect and adapt the work of the Developers, not to report on individual activities or performance 1 . The focus of the Daily Scrum should be on the collective work and progress of the Developers as a self-organizing team 2 .

The correct answer is B, because the guideline that a Scrum Master should give is that estimates are made by the Development Team. The Scrum Guide states that “the number of items selected from the Product Backlog for the Sprint is solely up to the Development Team. Only the Development Team can assess what it can accomplish over the upcoming Sprint.” Therefore, the Development Team should estimate the work in Scrum, using any method or unit they prefer.

According to the Scrum Guide 1 , when multiple Scrum Teams are working together on one product, they must coordinate their work with each other. One way to do this is through Nexus, a framework for scaling Scrum. Nexus helps to reduce cross-team dependencies and integration issues by making them more transparent. Multiple Scrum Teams working on one product use one Product Backlog.

The correct answer is D, because the recommended size for a Development Team is 3 to 9 members. The Scrum Guide states that “fewer than three Development Team members decrease interaction and results in smaller productivity gains. Smaller Development Teams may encounter skill constraints during the Sprint, causing the Development Team to be unable to deliver a potentially releasable Increment. Having more than nine members requires too much coordination. Large Development Teams generate too much complexity for an empirical process to be useful.”

 According to the Scrum Guide 1 , 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. Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team. The team model in Scrum is designed to optimize flexibility, creativity, and productivity.

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 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, when the Scrum Team gets caught in an internal disagreement about which development techniques to apply, two techniques that the Scrum Master could use are:

Involve the complete Development Team, as they are responsible for managing and refining their own work.

Use coaching techniques, such as open questions and active listening, to help the Development Team resolve their conflict and reach a consensus.

The other options are not appropriate, as they may undermine the self-organization and empowerment of the Developers.

The correct answer is E, because any of the above (or others) which are a decomposition of the selected Product Backlog items can be included in the Sprint Backlog. The Scrum Guide states that “the Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal.” Therefore, any work items that help the Development Team achieve the Sprint Goal can be part of the Sprint Backlog.