Definition of Done vs. Acceptance Criteria: What's the difference?
Tests your grasp of Agile quality gates. Define both, then contrast scope (global DoD vs. local AC) and ownership (Team vs. PO). Connect them to creating a shippable, valuable Increment. A red flag is treating them as interchangeable.
What's really being asked
This question assesses your practical experience with Agile quality frameworks, not just textbook definitions. The interviewer is probing your understanding of accountability, quality ownership, and the difference between a universal team standard (DoD) and a specific feature's requirements (AC). They want to see if you can connect these process artifacts to the ultimate goal: delivering a valuable, working product Increment that is truly 'done'.
The full answer
A strong answer addresses four key points in order. First, Definition and Scope: The Definition of Done (DoD) is a single, global checklist that applies to ALL work items, ensuring consistency. Acceptance Criteria (AC) are unique to a single Product Backlog Item (PBI), defining its specific requirements. Second, Purpose: The DoD ensures the Increment is of high quality and potentially shippable. The AC confirms a specific story is complete and delivers the intended user value. Third, Ownership: The entire Scrum Team (Developers, PO, Scrum Master) collaborates on and owns the DoD. The Product Owner is primarily responsible for writing AC, ideally in collaboration with the Developers. Fourth, Contribution to Value: AC ensures you built the right thing. The DoD ensures you built it the right way. Together, they create a valuable Increment.
The mistakes people make
A major red flag is using the terms interchangeably or suggesting the DoD is just a more technical set of AC. Another weak answer is defining the DoD as simply 'the ticket is moved to the Done column'—that describes a workflow state, not a quality standard. It's also a mistake to say only the Product Owner writes AC in a vacuum, or that only QA is responsible for the DoD. This signals a misunderstanding of collaborative, whole-team ownership. Finally, describing AC as a list of technical implementation tasks is incorrect; AC should focus on user-observable behavior and business value.
What usually comes next
Expect questions that dig into real-world application, such as: 'Tell me about a time you had to push back because an item didn't meet the Definition of Done.' Or, 'How would you handle a situation where the team consistently fails to meet its DoD?' Or, 'Describe how your team's Definition of Done has evolved over time.'
A concrete example
For a 'User Login' story, the Acceptance Criteria would be specific to that feature: 1. When a user enters correct credentials, they are logged in. 2. When a user enters incorrect credentials, they see an error message. The Definition of Done applies to this story AND all others: 1. Code is peer-reviewed. 2. Unit test coverage is above 85%. 3. All AC are met and verified by QA. 4. The feature is deployed to staging without breaking the build. 5. Any new secrets or configurations are documented.
Interview question
What is the fundamental difference in scope and purpose between the Definition of Done (DoD) and Acceptance Criteria (AC)?
- a.The DoD is a global quality standard for all work items, ensuring a shippable Increment, while AC are specific requirements for a single Product Backlog Item, ensuring its intended value.Correct
- b.The DoD is a checklist for moving a ticket to the "Done" column, and AC are technical specifications for testing.
- c.The DoD is solely created by the Development Team to track technical tasks, whereas AC are written by the Product Owner to define user stories.
- d.The DoD ensures a specific feature is complete and delivers user value, while AC guarantees the entire product increment is of high quality.
Why? this is the answer
The card states the DoD is a "single, global checklist that applies to ALL work items" ensuring a "potentially shippable Increment," while AC are "unique to a single Product Backlog Item, defining its specific requirements" and confirming it "delivers the intended user value." Option D incorrectly swaps these core purposes and scopes.
Just read this? Test yourself on what you have been reading.
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on agile — each one lists the topics its interview covers.
See open roles