New Release PSM-I Professional Scrum Master Questions

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 A. When multiple Scrum Teams work on the same product, they should share a common Definition of Done. This creates transparency across the product and ensures that all Increments are held to the same quality standard. Without one shared Definition of Done, it becomes difficult to inspect the integrated product accurately and determine whether work is truly complete.

Option B is incorrect because Scrum does not recommend separate Definitions of Done later reconciled in a hardening Sprint. Hardening Sprints are not part of Scrum and usually indicate that quality has not been built into normal development. Option C is also incorrect because merely making different definitions visible does not solve the inconsistency problem. A product needs one integrated standard of completion. Option D is incorrect because Scrum Masters do not define the Definition of Done on behalf of the teams. It must be mutually understood and used by the Scrum Teams working on that product, taking organizational standards into account.

A shared Definition of Done supports integration, quality, and releasability. It helps all teams contribute to one coherent product Increment rather than producing partially compatible outputs with differing completion standards.

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 of “Done” is created by the development organization (or Development Team if none is available from the development organization). The definition guides the Development Team in creating a “Done” Increment.

According to the Scrum Guide, two things that the Scrum Team should do during the first Sprint are building at least one piece of valuable functionality and creating at least one valuable, useful Increment. These are the goals of every Sprint, regardless of its order. The other options are not things that the Scrum Team should do during the first Sprint, as they are either out of scope (such as defining major product features and a release plan architecture or making a plan for the rest of the project) or unnecessary (such as analyzing, describing, and documenting requirements for subsequent Sprints).