B
BrainBOK
Dashboard
PricingStudy GuideFAQ
Sign InGet Started
DashboardITTO ExplorerQuizFlashcardsExamsStudy Guide
DashboardITTO ExplorerQuizFlashcardsExamsStudy Guide
Agile Guide

Agile Artifacts

Definition of Done

Explanation of definition of done in agile

You're viewing a free preview of the Study Guide. Upgrade to access all 500+ pages. Upgrade to Plus

Definition of Done is a team's checklist of all the criteria required to be met so that a deliverable can be considered ready for customer use.

Done = Releasable

Definition of Done (DoD) is at the Product level, and not story/feature/epic level. If a project team is releasing increments of the product with every iteration, then the product needs to meet the DoD at the end of each iteration.

Examples of DoD for a software product are:

  • Works on the latest versions of Chrome, Firefox and Safari
  • User acceptance testing (UAT) passed
  • eSecurity testing passed
  • Load testing passed
  • General Data Protection Regulation (GDPR) compliance testing passed

DoD increases transparency in the team by providing a shared understanding of what "Done" means. Without having a clear DoD, the team may end up having a pile of unreleasable work. DoD is usually defined at the beginning of the first iteration, but it can continue to evolve and change during the course of the project.

Definition of Done vs Acceptance Criteria

DoD is not the same as Acceptance Criteria, which is defined at the story/feature/epic level. For example, "flight search results in the application should be displayed in less than 5 secs" is an example of Acceptance Criterion.

The project team owns the DoD and they collaborate with the product owner to define it. Acceptance Criteria are defined by the product owner.

Further reading: Definition of Done vs Acceptance Criteria

Enjoying this article?

BrainBOK members get everything they need to pass the PMP or CAPM — all in one place.

  • 500+ Study Guide pages across all PMP & CAPM domains
  • 2,000+ practice exam questions with full explanations
  • ITTO Explorer — visual maps for all processes & knowledge areas
  • Adaptive flashcards for fast terminology recall
Create Free AccountSee Plans & Pricing
PreviousCumulative Flow Diagram (CFD) — Agile & PMP Exam GuideNextImpediments Backlog

0 / 45 completed

0%

Guide Index
  • Agile Overview
  • Agile Manifesto
  • Agile Life Cycles
  • Agile Triangle of Constraints
  • Agile Concepts Checklist
  • Agile Approaches and Methods
  • Scrum
  • Extreme Programming (XP)
  • Kanban for Project Management — PMP & PMI-ACP Exam Guide
  • Lean
  • Dynamic Systems Development Method (DSDM)
  • Scaled Agile Framework (SAFe®)
  • Crystal Methods
  • Agile Planning
  • Agile Estimation Techniques
  • Ideal Time
  • Story Point
  • Velocity
  • Agile Risk Management
  • Agile Contracts
  • Agile Suitability Filters
  • Transition to Agile
  • Shu Ha Ri Model
  • Project Manager's Role in Agile Projects
  • Effective Agile Teams
  • T-Shaped and I-Shaped Individuals
  • Agile Artifacts Overview
  • Backlog
  • Burndown and Burnup Charts
  • Cumulative Flow Diagram (CFD) — Agile & PMP Exam Guide
  • Definition of Done
  • Impediments Backlog
  • Information Radiators
  • User Story
  • Agile Practices Overview
  • Doing Agile vs Being Agile
  • Aggressive Transparency
  • Cadence and Timeboxing
  • Small Batch Size
  • Daily Standup Meetings
  • Fail Fast/Learn Quickly Mindset
  • Frequent Reviews
  • Inspect and Adapt
  • Retrospective
  • Sprint Changes