Definition of Done & Acceptance Criteria Flashcards
7 cards from real CAE practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Definition of Done & Acceptance Criteria flashcards as text
What is the primary purpose of the Definition of Done (DoD) in Scrum?
Answer: To define criteria that must be met before a Product Backlog Item is considered complete
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.
How does the Definition of Done differ from Acceptance Criteria?
Answer: The DoD applies to all Product Backlog Items while Acceptance Criteria are specific to individual user stories
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.
Who is responsible for creating and maintaining the Definition of Done in Scrum?
Answer: The entire Scrum Team
The Definition of Done is collaboratively created and maintained by the entire Scrum Team to ensure a shared understanding of what completeness means.
What should happen if a Product Backlog Item does not meet the Definition of Done at the end of a Sprint?
Answer: It should not be included in the Sprint Review or considered part of the Increment
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.
Which of the following is a typical element found in a Definition of Done?
Answer: Code reviewed by at least one peer
Peer code review is a common quality gate in a DoD that ensures code quality and knowledge sharing before work is considered complete.
What is the relationship between Acceptance Criteria and the Sprint Review?
Answer: Acceptance Criteria are used to demonstrate whether a user story's functionality has been delivered
During the Sprint Review, the team demonstrates completed work against each story's Acceptance Criteria to confirm that the required functionality was delivered correctly.
What does the INVEST acronym represent when evaluating user stories in Agile?
Answer: Independent, Negotiable, Valuable, Estimable, Small, Testable
INVEST stands for Independent, Negotiable, Valuable, Estimable, Small, Testable — a checklist of qualities that define a well-formed, actionable user story.