What is a Definition of Done (DoD), and how does it impact quality?

Definition:

The Definition of Done is a shared understanding of what “done” means for a backlog item

or Increment. It ensures transparency and consistent quality.

Impact on quality:

• Prevents incomplete work from being marked as finished.
• Reduces rework by setting clear expectations.
• Ensures the Increment is potentially shippable.

Example DoD:

• Code is committed and peer-reviewed
• Unit tests are written and passed
• Integrated into CI/CD pipeline
• User story accepted by Product Owner
• No major bugs in QA

Real-World Example:

Without a DoD, a team may claim a feature is “done” even though it hasn’t been tested.

With a proper DoD, it won’t be considered complete until it’s fully tested, reviewed, and

accepted.

Follow On: