CAE Definition of Done & Acceptance Criteria

Question 1

What is the primary purpose of the Definition of Done (DoD) in Scrum?

Accepted Answer

To define criteria that must be met before a Product Backlog Item is considered complete

Answer

The DoD is a shared understanding of what 'complete' means for all work, ensuring every team member agrees on completeness criteria before an Increment is accepted.

Question 2

How does the Definition of Done differ from Acceptance Criteria?

Accepted Answer

The DoD applies to all Product Backlog Items while Acceptance Criteria are specific to individual user stories

Answer

The DoD is a universal checklist applied to every work item, whereas Acceptance Criteria are specific, story-level conditions that define success for one particular feature.

Question 3

Who is responsible for creating and maintaining the Definition of Done in Scrum?

Accepted Answer

The entire Scrum Team

Answer

The Definition of Done is collaboratively created and maintained by the entire Scrum Team to ensure a shared understanding of what completeness means.

Question 4

What should happen if a Product Backlog Item does not meet the Definition of Done at the end of a Sprint?

Accepted Answer

It should not be included in the Sprint Review or considered part of the Increment

Answer

Work that does not meet the DoD cannot be part of the potentially releasable Increment and must be returned to the Product Backlog for a future Sprint.

Question 5

Which of the following is a typical element found in a Definition of Done?

Accepted Answer

Code reviewed by at least one peer

Answer

Peer code review is a common quality gate in a DoD that ensures code quality and knowledge sharing before work is considered complete.

(CAE) Certified Agile Essentials Specialist Practice Test

(CAE) Certified Agile Essentials Specialist Practice Test

CAE Definition of Done & Acceptance Criteria