Definition of Done (DoD)

Definition of Done (DoD) is a shared, agreed-upon set of criteria that determines when a user story, feature, or increment is considered complete.

DoD answers: “What does ‘done’ really mean?”

1. Definition

Definition of Done (DoD) is a shared, agreed-upon set of criteria that determines when a user story, feature, or increment is considered complete.

DoD answers: “What does ‘done’ really mean?”

2. Purpose of Definition of Done

• Create a common understanding of completion
• Ensure consistent quality standards
• Prevent incomplete or partially tested work
• Support predictable releases

3. Typical DoD Checklist (Manual Testing Focus)

A story is considered Done when:

• Acceptance criteria are fully met
• Functional testing completed
• Regression impact assessed
• No open Critical or High defects
• Test cases executed and updated
• Defects logged, tracked, and verified
• Documentation updated (if required)
• Product Owner accepts the story

4. Manual Tester’s Role in DoD

• Validate acceptance criteria
• Ensure testing completeness
• Confirm defect status
• Provide test sign-off input
• Ensure quality standards are met

5. DoD vs Acceptance Criteria

6. DoD vs Definition of Ready (DoR)

7. Real-Time Example

A story is not Done if:

• Acceptance criteria pass but regression breaks
• High-severity defect remains open

8. Benefits of Strong DoD

• Higher quality increments
• Reduced rework
• Clear release readiness
• Strong trust with stakeholders

9. Common Mistakes

• Vague DoD definitions
• Ignoring testing activities in DoD
• Changing DoD frequently without alignment

10. Interview-Ready Answers

Short answer:

Definition of Done defines the criteria that determine when work is considered complete.

Detailed answer:

DoD is a shared checklist that ensures a user story or increment meets agreed quality standards before being marked as complete.

11. Key Takeaway

Definition of Done ensures quality is built-in, verified, and agreed upon, not assumed.