PSM I exam question

Answering: “Which of these may a Scrum Team deliver at the end of a Sprint?” (PSM I)

By Hiro TakashimyaUpdated
Studying for the PSM I exam? Try 20 free practice questions first.Start the free quiz →

At the end of a Sprint, a Scrum Team delivers a valuable, useful Increment that meets the Definition of Done. Software with known bugs, a lone document or failing tests do not count.

Exam Question

Which of these may a Scrum Team deliver at the end of a Sprint?
(choose the best answer)
A. A valuable, useful Increment that meets the Definition of Done.
B. An increment of software with minor known bugs in it.
C. A single document, if that is what management asked for.
D. Failing unit tests, to identify acceptance tests for the next Sprint.

Correct Answer

A. A valuable, useful Increment that meets the Definition of Done.

Why This Is the Correct Answer

The Scrum Guide says “Work cannot be considered part of an Increment unless it meets the Definition of Done.” It also says that to provide value, the Increment must be usable. The Scrum Team is accountable for creating such an Increment every Sprint. Delivering work with known defects, or work that fails its tests, would mislead stakeholders about the product’s state. A single document may be useful, but on its own it is not a usable step toward the Product Goal. Insisting on Done work every Sprint keeps the Increment transparent and gives stakeholders something real to inspect at the Sprint Review.

Why the Other Options Are Wrong

B. Software with minor known bugs. If the bugs break the Definition of Done, the work is not Done. Known defects create hidden debt.

C. A single document, if management asked for it. Management requests do not change what an Increment is. A document alone is rarely a usable product increment.

D. Failing unit tests to identify future acceptance tests. Failing tests mean the work does not meet the Definition of Done.

Exam Tip

When asked what a team may deliver, the answer is always a Done, usable Increment. Options that soften quality for any reason are wrong.

Key Takeaways

  • Each Sprint delivers a usable Increment.
  • The Increment must meet the Definition of Done.
  • Management requests do not lower the quality bar.

You cannot copy content of this page