Definition of Done vs. Acceptance Criteria: Clearing Up the Agile Confusion for PMP

Two Quality Concepts That Candidates Constantly Confuse

One of the most common points of confusion among PMP candidates studying agile content is the difference between Definition of Done and acceptance criteria. Both relate to quality — both define when something is considered complete and acceptable — but they operate at different levels and serve different purposes. The PMP exam tests this distinction, and candidates who confuse the two consistently select wrong answers on agile quality questions.

Understanding this distinction is not just academic. In practice, confusing DoD and acceptance criteria leads to inconsistent quality standards, arguments about what "done" means, and deliverables that meet user requirements but are not production-ready — or that are technically complete but do not satisfy user needs. Both concepts are necessary, and they complement rather than replace each other.

Acceptance Criteria: Story-Specific Quality

Acceptance criteria are the conditions that must be true for a specific user story to be considered correctly implemented. They are unique to each story because each story describes a different user need. Acceptance criteria answer the question: "Does this feature work correctly for the user?"

For a user story about password reset functionality, acceptance criteria might include specifications like the user receives a reset email within 60 seconds of requesting it, the reset link expires after 24 hours, the user must create a password that meets complexity requirements, and the user is redirected to the login page after successfully resetting their password. These criteria are specific to this one story and would not apply to other stories.

Acceptance criteria are defined by the product owner in collaboration with the development team before development begins. They represent the product owner's expectations for how the feature should work. The product owner uses these criteria during the sprint review to verify that the story has been implemented correctly.

On the PMP exam, acceptance criteria connect to scope validation — verifying that deliverables meet stakeholder requirements. They are the agile equivalent of acceptance testing criteria in traditional project management.

Definition of Done: Universal Quality Standard

The Definition of Done is a shared understanding of what it means for any work item to be considered complete. It applies equally to every user story, every feature, and every increment. DoD answers the question: "Is this work truly finished and ready for production?"

A typical Definition of Done might include that the code has been written and peer-reviewed, unit tests have been written and pass, integration tests pass, the feature has been tested against acceptance criteria, the code meets the team's coding standards, documentation has been updated, security review has been completed, performance requirements have been verified, and the feature has been deployed to the staging environment and verified.

The Definition of Done is owned by the development team and applies consistently across all work. It represents the team's quality standard — the minimum bar that every piece of work must clear before it can be considered complete. Unlike acceptance criteria, which change with each story, the DoD remains stable across stories, though it may evolve over time as the team's capabilities and standards improve.

The Critical Difference

The simplest way to understand the difference is this: acceptance criteria define what to build, while the Definition of Done defines how well to build it. A story can meet all its acceptance criteria — the feature works as the product owner specified — but not meet the Definition of Done if the code has not been reviewed, tests have not been written, or documentation has not been updated. Conversely, a piece of work can meet the Definition of Done — all processes have been followed, all quality checks have passed — but fail acceptance criteria if the feature does not work as specified.

Both must be satisfied for a story to be considered truly complete. Acceptance criteria ensure the feature delivers the right value to the user. Definition of Done ensures the feature is built to a standard that supports long-term product quality, maintainability, and reliability.

An Analogy

Think of building a house. Acceptance criteria are like the homeowner's specifications — the kitchen should have granite countertops, the master bedroom should face south, and there should be a two-car garage. The Definition of Done is like the building code and construction standards — all wiring must meet electrical code, all plumbing must be pressure-tested, all structural connections must be inspected, and the certificate of occupancy must be obtained.

A house that meets the homeowner's specifications but violates building code is not done. A house that passes all inspections but does not have the kitchen the owner wanted does not meet acceptance criteria. Both conditions must be satisfied for the house to be considered complete and acceptable.

How the PMP Exam Tests This Distinction

PMP exam questions about DoD versus acceptance criteria often present scenarios where one is met but the other is not, and ask what should happen.

A common scenario describes a team that has implemented a feature that passes the product owner's review but has not completed code review or testing. The correct answer is that the story is not done because it does not meet the Definition of Done, regardless of whether the acceptance criteria are met. The PMP exam considers work incomplete if either condition is unsatisfied.

Another scenario might describe a team debating whether to include performance testing in their Definition of Done. The correct answer recognizes that the DoD should include all activities necessary for the increment to be potentially releasable — and performance testing that is deferred creates technical debt that accumulates and eventually slows the team.

Evolving the Definition of Done

The Definition of Done should evolve as the team's capabilities grow and as the organization's quality expectations change. An initial DoD for a new team might include basic items — code written, tests pass, code reviewed. As the team matures, the DoD expands to include more rigorous standards — automated performance testing, security scanning, accessibility verification, and deployment automation.

The PMP exam may test this evolution concept through retrospective scenarios where the team discusses expanding their DoD based on quality issues they have experienced. Expanding the DoD is a quality improvement activity that increases short-term effort per story but reduces long-term defects and technical debt.

Definition of Done in Hybrid Projects

In hybrid projects where some components use agile and others use predictive approaches, the Definition of Done applies to the agile components while traditional quality management processes apply to the predictive components. The project manager must ensure that quality standards are consistent across both approaches and that integration between agile and predictive components meets quality requirements.

The PMP exam may present hybrid scenarios where the Definition of Done for agile components must account for integration requirements with predictive components — for example, including integration testing with the predictive components as a DoD item for the agile team's increments.

Mastering the distinction between Definition of Done and acceptance criteria gives you a clear framework for answering agile quality questions on the PMP exam. Both concepts are about quality, but they address different dimensions of quality — acceptance criteria ensure value delivery, and Definition of Done ensures product integrity. The PMP exam expects you to understand and apply both.