Definition of Done vs Acceptance Criteria: PMP Exam Clarity

A Distinction the PMP Exam Loves to Test

Definition of Done (DoD) and acceptance criteria are two of the most frequently confused concepts in agile project management. The PMP exam exploits this confusion with scenario questions that require you to know exactly which applies. Getting this distinction right can be the difference between a correct and incorrect answer.

What Is the Definition of Done?

The Definition of Done is a shared understanding across the Scrum Team of what it means for work to be complete. It applies to every Product Backlog item and every Increment. Think of it as the team's quality standard — a checklist that must be satisfied before any work can be called "done."

Example Definition of Done

Code is written and peer-reviewed
Unit tests are written and passing
Integration tests pass
Code is deployed to the staging environment
Documentation is updated
Product Owner has reviewed the functionality

The DoD is created by the team (or the organization, if a standard exists) and applies uniformly. It doesn't change from story to story — it's the baseline quality bar.

What Are Acceptance Criteria?

Acceptance criteria are specific conditions that a particular user story or Product Backlog item must satisfy to be accepted by the Product Owner. They are unique to each story and define the boundaries of what that story delivers.

Example Acceptance Criteria

For a user story "As a user, I want to reset my password via email":

The user receives a reset link within 2 minutes of requesting it
The reset link expires after 24 hours
The new password must meet complexity requirements (8+ characters, one uppercase, one number)
The user is notified via email after a successful password change
Previous sessions are invalidated after the password is changed

The Key Differences

Here's a clear comparison to anchor your understanding:

Scope: DoD applies to all items. Acceptance criteria apply to one specific item.
Who creates it: DoD is set by the team (or organization). Acceptance criteria are defined by the Product Owner in collaboration with the team.
When it changes: DoD evolves slowly through retrospectives. Acceptance criteria are written fresh for each story during refinement.
What it measures: DoD ensures quality and completeness. Acceptance criteria ensure the right thing was built.

How They Work Together

Both must be satisfied for a story to be considered complete. A story could meet all its acceptance criteria (the feature works as specified) but not meet the DoD (tests weren't written, code wasn't reviewed). In that case, the story is not done.

Conversely, a story could meet the DoD (code reviewed, tests passing, deployed to staging) but fail acceptance criteria (the password reset link doesn't expire after 24 hours). Again, not done.

PMP Exam Applications

Watch for these exam scenarios:

"The Product Owner refuses to accept a completed feature even though it meets the Definition of Done." — Check if the acceptance criteria were met. The DoD is necessary but not sufficient.
"A team is unsure what 'done' means and every sprint ends with debates about completeness." — The team needs to establish (or clarify) their Definition of Done.
"A story was deployed to production but doesn't handle edge cases the Product Owner expected." — This is likely a failure to define adequate acceptance criteria during refinement.

Remember This for Exam Day

DoD = team-wide quality standard (the "how well"). Acceptance criteria = story-specific requirements (the "what exactly"). Both must be met. Neither replaces the other.

Solidify this concept and others by testing yourself with PMPprep's agile-focused practice questions.