Course contentsShow
← Software Engineering
Lesson 149 of 1,9334. Requirements EngineeringFree lesson

Acceptance Criteria vs Definition of Done

Distinguishing story-specific acceptance criteria from team-wide definition of done standards like code review and tests.

Acceptance Criteria vs Definition of Done

What you'll learn: How to distinguish story-specific acceptance criteria from universal quality standards that apply to all work.

The Core Difference

When working on user stories, you encounter two important quality gates: Acceptance Criteria and Definition of Done. Though they sound similar, they serve different purposes.

Acceptance Criteria are specific to one user story. They describe what makes that particular feature complete and correct. For example, a login story might require "User can log in with email and password" and "Error message displays for invalid credentials."

Definition of Done applies to every story your team works on. It's a checklist of quality standards that must be met before any work is considered complete—things like "Code has been reviewed by a peer," "All tests pass," "Documentation is updated," or "No linting errors."

A Helpful Analogy

Think of building custom furniture:

  • Acceptance Criteria = The customer's specifications for this table: "Must be 6 feet long, oak wood, seats 8 people"
  • Definition of Done = Your workshop's quality standards for all furniture: "All edges sanded smooth, two coats of finish applied, assembly instructions included"

Why Both Matter

Acceptance Criteria ensure you built the right thing for this specific need. Definition of Done ensures you built it the right way according to team standards. You might satisfy acceptance criteria but still fail the definition of done if you skipped code review or forgot tests.

The Definition of Done typically includes technical practices that maintain code quality and team velocity over time, while acceptance criteria focus on business value and functional correctness for that story alone.

Key Takeaway: Acceptance criteria are story-specific functional requirements; definition of done is your team's universal quality checklist that applies to every piece of work.