Free Scrum PSM-I Exam Dumps June 2026

The correct answer is B, because the time-box for the Sprint Planning meeting is 8 hours for a monthly Sprint. The Scrum Guide states that ''Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.''

According to the Scrum Guide1, the Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Developers on why it is building the Increment. It also provides a basis for inspecting and adapting during the Sprint Review and Sprint Retrospective. The Sprint Goal is a result of Sprint Planning, as is the Sprint Backlog.

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, one good way for a Scrum Team to ensure security concerns are satisfied is to add security concerns to the definition of ''Done''. Another good way is to have the Scrum Team create Product Backlog items for each concern, as they are responsible for managing and refining the Product Backlog.

According to the Scrum Guide, multiple Scrum Teams working on the same product do not have to have the same Sprint start date. They may start their Sprints at different times, as long as they synchronize their work and integrate their Increments at least by the end of each Sprint. The other option is not valid, as it implies that having the same Sprint start date is mandatory for multiple Scrum Teams.

Two techniques that the Scrum Master could use when the Scrum Team gets caught in an internal disagreement about which agile practices to apply are to involve the complete Scrum Team in making a decision, and to use coaching techniques such as open questions and active listening, as stated in [3]: ''The Scrum Master should facilitate a constructive dialogue among the team members and help them reach a consensus on which agile practices to use. The Scrum Master should also use coaching techniques such as open questions and active listening to understand the underlying needs and motivations of each team member and to help them find common ground.''

According to the Scrum Guide1, one aspect of Scrum Teams inspecting how they work toward their Product Goal is that they improve their definition of ''Done'' over time. 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. Therefore, it is most appropriate for a Development Team to change the definition of ''Done'' during the Sprint Retrospective.

The correct answer is A, because Development Team membership should change as needed, while taking into account a short term reduction in productivity. The Scrum Guide states that ''development Teams are cross-functional, with all of the skills as a team necessary to create a product Increment; 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, changing Development Team membership may affect their cross-functionality and self-organization in the short term.