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
How should Acceptance Criteria be written to be most effective in Agile?
Answer: As clear, testable conditions that define when a story is complete
Effective Acceptance Criteria are specific, measurable, and testable conditions that confirm a user story has been implemented correctly and meets the customer's need.
The Given-When-Then (GWT) format for writing Acceptance Criteria is associated with which practice?
Answer: Behavior-Driven Development (BDD)
The Given-When-Then format originates from Behavior-Driven Development (BDD) and structures Acceptance Criteria as scenarios that describe system behavior from the user's perspective.
What does it mean for the Definition of Done to evolve over time?
Answer: The DoD may become more stringent as the team improves its practices
As teams mature and build capability, they typically strengthen their DoD by adding more quality checks, reflecting their growing ability to meet higher standards consistently.
What is the primary risk of having an unclear or weak Definition of Done?
Answer: Technical debt may accumulate as incomplete work is incorrectly considered done
A weak DoD allows work to be called 'done' without meeting proper quality standards, causing hidden technical debt that grows and eventually slows the team's velocity.
In Agile, what is meant by 'undone work'?
Answer: Work that was marked complete but does not fully meet the Definition of Done
'Undone work' refers to work that appears complete but has unmet DoD criteria, creating hidden technical debt that must be addressed in a future Sprint.
Which Agile Manifesto principle best supports the use of Acceptance Criteria to measure progress?
Answer: Working software is the primary measure of progress
The principle that working software is the primary measure of progress is directly supported by Acceptance Criteria, which define precisely what 'working' means for each feature.
When should Acceptance Criteria be defined for a user story?
Answer: Before or during Sprint Planning so the team understands scope before committing
Acceptance Criteria should be defined before or during Sprint Planning so the team understands exactly what success looks like before committing to deliver the story.