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

The correct answer is B, because when multiple Scrum Teams work from the same Product Backlog, they should pull in work in agreement with the Product Owner. The Scrum Guide states that “multiple Scrum Teams often work together on the same product. One product goal unites them. Therefore, they must mutually define and comply with a definition of ‘Done’ that applies to their combined work product.” Therefore, they should collaborate and coordinate with each other and with the Product Owner to select Product Backlog items that align with their shared product goal.

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

References: Scrum Guide, Nexus Guide

According to the Scrum Guide, two intended outcomes of the Daily Scrum are identification of impediments that may prevent the Developers from achieving the Sprint Goal and a shared understanding of the most important work to be undertaken next to achieve the best possible progress toward the Sprint Goal. These outcomes help the Developers to inspect their progress, plan their work, and collaborate effectively. 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 a status report or an update of completed tasks).

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 Backlog1. The Scrum Master can help the Developers remove these impediments or find ways to overcome them2.

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 Goal1. 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 work1. 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 else2. The Developers are responsible for conducting and facilitating the Daily Scrum, not the Scrum Master1. 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 timebox2.

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 stakeholders1. 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 Goal3.

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 management2. The purpose of the Daily Scrum is to inspect and adapt the work of the Developers, not to report on individual activities or performance1. The focus of the Daily Scrum should be on the collective work and progress of the Developers as a self-organizing team2.

The correct answers are A, C, and E, because these are feedback loops in Scrum. The Sprint Review is a feedback loop that allows the Scrum Team and the stakeholders to inspect the Increment and adapt the Product Backlog. The Sprint Retrospective is a feedback loop that allows the Scrum Team to inspect itself and create a plan for improvements. The Daily Scrum is a feedback loop that allows the Development Team to inspect its progress and plan its work for the next 24 hours.

The correct answer is C, because if necessary, the Development Team is responsible for removing a team member who is creating a hostile environment. 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 should manage its own composition and dynamics, and may need help from the Scrum Master to facilitate this process.

According to the Scrum Guide1, each event in Scrum is a formal opportunity to inspect and adapt something. These events are specifically designed to enable critical transparency and inspection. Failure to include any of these events results in reduced transparency and is a lost opportunity to inspect and adapt. All events are time-boxed events, such that every event has a maximum duration. Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened. The remaining events may end whenever the purpose of the event is achieved, ensuring an appropriate amount of time is spent without allowing waste in the process. The time-box for the Sprint Review is four hours for a one-month Sprint.

References: Scrum Guide

According to the Scrum Guide, the Developers are accountable for tracking the remaining work toward the Sprint Goal, 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 someone else outside the Development Team (such as the Scrum Master, the Product Owner, or the Project Manager) is accountable for tracking the remaining work, which is not consistent with Scrum values and principles.

The correct answer is C, because when a Development Team is having trouble delivering a working Increment because they don’t understand a functional requirement, they should collaborate with the Product Owner to determine what is possible and acceptable. The Scrum Guide states that “the Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team. How this is done may vary widely across organizations, Scrum Teams, and individuals.” Therefore, the Product Owner should clarify the functional requirement and negotiate the scope of work with the Development Team.

According to the Scrum Guide, the action that the Scrum Master should take when the Team decides that a Sprint Retrospective is unnecessary is to begin facilitating productive and useful Sprint Retrospectives. The Sprint Retrospective is an essential event for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. The Scrum Master is responsible for ensuring that this event takes place and that positive outcomes are achieved. The other options are not valid actions, as they either imply that the Scrum Master complies with or ignores the decision of the Team (such as complying with it, calling a meeting with senior management, or consulting with the Product Owner), which is not consistent with Scrum values and principles.