Scrum PSM-I Dumps - Pass Professional Scrum Master I Exam in 2026

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

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.

According to the Scrum Guide1, the Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning. The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Product Owner is part of the Scrum Team and should participate as a Scrum Team member in the Sprint Retrospective.

The correct answers are B and D, because adding non-functional requirements to the Product Backlog and keeping the Product Owner posted on the expected effort helps prioritize and plan them in alignment with the product vision and goals. Additionally, adding non-functional requirements to the definition of 'Done' ensures that they are met every Sprint and do not accumulate technical debt.

The correct answer is B because cross-functional teams in Scrum are not optimized to work on only one component or one technical layer of a system. A cross-functional Scrum Team has all the skills necessary to create value each Sprint and deliver a usable Increment. This means the team should be capable of working across the different skills and disciplines needed to complete Product Backlog items according to the Definition of Done.

If a team is organized around only one component or specialty, it creates handoffs, dependencies, and silos. Those conditions reduce agility and make it harder to deliver a complete Increment each Sprint. Scrum instead favors teams that can collaborate across analysis, design, development, testing, and other needed capabilities so they can produce finished product value rather than partial technical output.

Cross-functionality supports self-management and reduces delays caused by waiting on other specialists or teams. It helps the Scrum Team focus on outcomes instead of isolated activities. In Scrum, the goal is not local optimization of a single layer or function. The goal is delivering complete, useful, high-value Increments frequently and transparently.