PSM I Practice Question

Defining Done: Key Purposes of the Scrum Definition of Done

Get 212 more PSM I practice questions

Complete explanations included

$25 - Get Questions

Question

Developers select a set of Product Backlog items for a Sprint Backlog with the intent to get the selected items done by the end of the Sprint. Which three phrases best describe the purpose of a Definition of Done?(choose the best three answers)

Options

  • A A. It provides a template for elements that need to be included in the documentation.
  • B B. It guides the Developers in creating a forecast at the Sprint Planning.
  • C C. It controls whether the developers have performed their tasks.
  • D D. It tracks the percent completeness of a Product Backlog item.
  • E E. It creates transparency over the work inspected at the Sprint Review.
  • F F. It defines what it takes for an Increment to be ready for release.

Answer

  • B. It guides the Developers in creating a forecast at the Sprint Planning.
  • E. It creates transparency over the work inspected at the Sprint Review.
  • F. It defines what it takes for an Increment to be ready for release.

Explanation

The Definition of Done (DoD) plays a crucial role in Scrum by ensuring that all work is completed to a consistent standard. Option B is correct because the DoD helps Developers create a reliable forecast during Sprint Planning by clarifying what 'done' means for each Product Backlog item. This allows for better planning and commitment. Option E is also correct as the DoD creates transparency during the Sprint Review, enabling stakeholders to understand what work has been completed and what is still pending. Lastly, Option F is correct because the DoD defines the criteria that must be met for an Increment to be considered ready for release, ensuring quality and usability. Each of these options underscores the importance of having a clear, agreed-upon definition that guides the team throughout the Sprint.

Expert Author

MR

Marcus Rodriguez

Product Owner & Business Analyst

Backlog management, stakeholder collaboration, user stories

Why Other Options Are Wrong
Option A is incorrect because while documentation is important, the DoD does not serve as a template for documentation elements; it focuses on the quality and completeness of work. Option C is misleading as the DoD does not control developers' actions but rather serves as a guideline for what is considered complete. Finally, Option D is inaccurate because the DoD does not track percentage completeness; it defines the qualitative aspects that must be satisfied for an item to be considered done, not a metric or progress tracker.
Real-World Application
In a real-world Scrum team, during Sprint Planning, the Developers refer to their Definition of Done, which includes criteria such as 'code reviewed', 'tested', and 'documented'. This allows them to select Product Backlog items confidently, knowing they can meet these criteria by the end of the Sprint. When they present their work at the Sprint Review, stakeholders see that all items meet the DoD, creating trust and transparency.
Common Pitfalls
  • Assuming everyone understands the DoD in the same way
  • Not updating the DoD as the team's understanding of quality evolves
  • Using the DoD as a checklist rather than a guiding principle

Key Concepts

Definition of Done Sprint Planning Transparency Increment Quality Assurance

Scrum Guide Reference

Scrum Guide 2020, Section 3.10: Definition of Done

Want More PSM I Practice Questions?

Get 212 additional questions with detailed explanations.