Definition of Done (DoD) in Scope Performance Domain

PMBOK v8 Definition

The Definition of Done (DoD) is a checklist of all the criteria required to be met so that a deliverable can be considered ready for customer use. In projects using an adaptive approach, a DoD is a shared understanding of the specific criteria that should be met before a piece of work (e.g., a user story, feature, or increment) is considered complete and ready for release to the next stage or the customer. This concept belongs to the Scope Performance Domain and is applied within the processes of defining, developing, monitoring, controlling, and verifying scope.

Why It Matters for the Exam

The DoD is frequently tested on the PMI exam because it directly connects scope validation, quality management, and stakeholder satisfaction. Expect questions that test your ability to distinguish the DoD from acceptance criteria, and to identify when a deliverable is truly "done" versus merely "completed" in terms of tasks. Questions appear in situational scenarios, particularly in adaptive and hybrid project contexts.

Key Points to Remember (for the exam)

• Core Purpose: The DoD is a checklist of criteria that must be met before a deliverable is considered ready for customer use—not just technically complete.
• Adaptive Projects: In adaptive approaches, the DoD is a shared understanding among the team, applied to user stories, features, or increments.
• Scope Performance Domain: The DoD supports the Scope domain's objective to ensure that only required work is performed, optimizing costs and schedule to maximize value.
• Quality Connection: The DoD directly supports quality by ensuring deliverables meet specified acceptance criteria and stakeholder expectations.
• Not Acceptance Criteria: DoD is about completeness of the work; acceptance criteria are about whether the customer accepts the deliverable.
• Verification Tool: The DoD is used to verify scope—confirming that deliverables meet the defined criteria before release to the next stage or customer.
• Continuous Process: The DoD should be defined, developed, monitored, validated, and controlled based on the project life cycle.

Typical PMI Exam Example

A software development team using Scrum has a user story: "As a user, I want to reset my password." The team's DoD includes: code reviewed, unit tests passed, integration tested, documentation updated, and feature demoed to the product owner. During the sprint review, the feature works but documentation is incomplete. Question: Is the user story "done"? Answer: No—because the DoD criteria are not fully met.

PMI Exam Traps

• Trap: Confusing DoD with acceptance criteria

  • Reality: DoD is a checklist for completeness of work; acceptance criteria are conditions for customer acceptance

• Trap: Thinking DoD applies only to the final project deliverable

  • Reality: DoD applies to each increment, user story, or feature in adaptive projects

• Trap: Assuming DoD is optional or team-defined without stakeholder input

  • Reality: DoD must be a shared understanding, aligned with stakeholder expectations and quality standards

• Trap: Believing DoD is the same as the project scope statement

  • Reality: DoD is a detailed checklist for each work item; scope statement is a high-level description of project, product, and value

Important PMI Connections

Quick Review Questions

1. In an adaptive project, what is the Definition of Done (DoD) primarily used to determine?
2. A team completes all development tasks for a feature but has not run integration tests. According to the DoD, is the feature ready for customer use?
3. How does the DoD support the Scope Performance Domain's objective of maximizing project value?
4. What is the key difference between the DoD and acceptance criteria in a predictive project?
5. In a hybrid project, who should establish the shared understanding of the DoD?

PMBOK v8 Reference

Section 2.2 – Scope Performance Domain (Key Concepts and Processes)