Which term is the Definition of Done?

Which term is the Definition of Done?

• A. Definition of Done
• B. Definition of Ready
• C. Acceptance Criteria
• D. Quality Gate

Answer: (A)

The Definition of Done is the explicit, shared set of criteria that must be met for a backlog item to be considered complete and potentially releasable. It goes beyond just “working” functionality to include quality aspects such as code being implemented, tests passing (unit and integration), code integrated with the mainline, documentation updated, and any acceptance or release criteria satisfied. This shared completion standard ensures transparency and predictability in delivery because everyone knows what "done" means. Definition of Ready, in contrast, is about the prerequisites that must exist before work can start, not about finishing. Acceptance Criteria specify the conditions for the item’s functionality to be accepted by the Product Owner, but they don’t necessarily cover all quality and process steps required for done. A Quality Gate is a gating checkpoint in the process, not the formal completion state for the item. Example of a DoD might include: code complete, automated tests passing with required coverage, builds successful and integrated, feature deployed to staging, documentation updated, and Product Owner sign-off.

The Definition of Done is the explicit, shared set of criteria that must be met for a backlog item to be considered complete and potentially releasable. It goes beyond just “working” functionality to include quality aspects such as code being implemented, tests passing (unit and integration), code integrated with the mainline, documentation updated, and any acceptance or release criteria satisfied. This shared completion standard ensures transparency and predictability in delivery because everyone knows what "done" means.

Definition of Ready, in contrast, is about the prerequisites that must exist before work can start, not about finishing. Acceptance Criteria specify the conditions for the item’s functionality to be accepted by the Product Owner, but they don’t necessarily cover all quality and process steps required for done. A Quality Gate is a gating checkpoint in the process, not the formal completion state for the item.

Example of a DoD might include: code complete, automated tests passing with required coverage, builds successful and integrated, feature deployed to staging, documentation updated, and Product Owner sign-off.