Answering: “Why does the Product Owner want the Developers to adhere to its Definition of Done?” (PSM I)

The Product Owner wants the Developers to follow the Definition of Done so there is complete transparency into what has actually been done each Sprint. It is not a tool for predicting productivity or punishing missed velocity.

Exam Question

Why does the Product Owner want the Developers to adhere to its Definition of Done?
(choose the best answer)
A. To predict the team’s productivity over time.
B. To know what the team will deliver over the next three Sprints.
C. To be able to reprimand the team when they don’t meet their velocity goal for the Sprint.
D. To have complete transparency into what has been done at the end of each Sprint.

Correct Answer

D. To have complete transparency into what has been done at the end of each Sprint.

Why This Is the Correct Answer

The Scrum Guide says the Definition of Done “creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment.” The Product Owner relies on that shared meaning to decide what to release, how to order the Product Backlog next, and what to tell stakeholders. If done meant different things from item to item, the Product Owner could not trust what is presented at the Sprint Review. Adhering to the Definition of Done keeps the Increment honest.

Why the Other Options Are Wrong

A. To predict the team’s productivity over time. The Definition of Done is about quality and transparency, not productivity forecasting.

B. To know what the team will deliver over the next three Sprints. The Definition of Done describes completed work. It does not forecast future delivery.

C. To reprimand the team for missing velocity goals. Scrum has no velocity goals, and using artifacts to blame people destroys trust.

Exam Tip

Connect the Definition of Done with transparency and quality. Answers about forecasting, productivity or control are traps.

Key Takeaways

• The Definition of Done shows what is really finished.
• The Product Owner depends on it for release decisions.
• It is not a forecasting or disciplinary tool.