Free Practice Questions for Scrum PSM-I Exam

The correct answer is A, because the Product Owner does not need to be present at the Daily Scrum. The Scrum Guide states that “the Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. … The structure of the meeting is set by the Development Team and can be conducted in different ways if it focuses on progress toward the Sprint Goal.” Therefore, the Daily Scrum is an internal event for the Development Team, and the Product Owner can attend only if invited by the Development Team.

According to the Scrum Guide, a Sprint concludes when the Sprint Retrospective is complete. This is the last event of the Sprint cycle, where the Scrum Team inspects itself and creates a plan for improvements. The other options are not valid indicators of the conclusion of a Sprint, as they are either irrelevant (such as the Product Owner deciding enough has been delivered) or incomplete (such as all tasks or Product Backlog items being done).

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 , 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 other roles are not responsible for making sure everyone on the Development Team does their tasks for the Sprint.

 According to the Scrum Guide, a Scrum Team is not only allowed to meet with stakeholders during Sprint Review, but also during Sprint Planning and throughout the Sprint as needed. The Sprint Review is an opportunity for the Scrum Team and the stakeholders to collaborate on what was done in the Sprint and what to do next. However, it is not the only time that stakeholder feedback is welcomed and valued.

The correct answer is A, because the Product Owner does not determine how many Product Backlog items the Development Team selects for a Sprint. 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 is responsible for choosing the scope of work for a Sprint.

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.

According to the Scrum Guide, a Scrum Team is cross-functional if it includes skilled individuals who together have all the skills necessary to create value each Sprint. This means that the Developers can work on any aspect of the product without depending on others outside the team. The other options are not valid descriptions of cross-functionality, as they either imply that the Developers work in silos or rely on external people (such as business analysts, architects, testers, or separate teams).

The best answer is C. When multiple Scrum Teams are working together on a product, they must mutually define and comply with the same Definition Of Done.

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 Scrum Guide also states that “when multiple Scrum Teams are working together on a product, they must mutually define and comply with the same Definition of Done. This ensures transparency and consistency among the teams and makes their combined work potentially releasable.”

A, B, and D are not correct answers.

A. Each Scrum Team uses its own, but must make their definition clear to all other teams so the differences are known.

This answer does not reflect the Scrum value of alignment 2 . Having different Definitions of Done for each Scrum Team can create confusion and inconsistency in the quality and completeness of the product. It can also make it difficult to integrate and deliver a coherent and valuable Increment at the end of each Sprint.

B. The Scrum Masters from each Scrum Team define a common Definition of Done.

This answer does not reflect the Scrum principle of self-organization 3 . The Definition of Done should be created by the Developers who are responsible for delivering the Increment, not by the Scrum Masters who are responsible for facilitating and coaching the Scrum Teams. The Scrum Masters can help the Developers understand and apply the Definition of Done, but they should not impose it on them.

D. Each Scrum Team defines and uses its own. The differences are discussed and reconciled during a hardening Sprint.

This answer does not reflect the Scrum value of focus 2 . Having different Definitions of Done for each Scrum Team can lead to technical debt or rework that requires a hardening Sprint to resolve. A hardening Sprint is an anti-pattern that violates the rule of delivering a potentially releasable Increment at the end of each Sprint 4 .