...
/Key Principle: Create and Use a Definition of Done
Key Principle: Create and Use a Definition of Done
Learn how a clear Definition of Done minimizes the gap between defect insertion and detection.
A clear Definition of Done (DoD) supports minimizing the gap between defect insertion and detection by ensuring that QA work on an item is performed close to all other work.
A good DoD will include completion criteria for design, code, test, documentation, and all other work related to implementation of a requirement. Completion criteria are ideally stated in terms that are unambiguously true or false. Here is an example DoD:
Teams need to define their own Definition of Done with factors that are relevant to their circumstances. In addition to the factors shown in the example above, a Definition of Done could include:
-
Product Owner accepts the item
-
Conforms to UI style guide
-
Passes acceptance tests
-
Passes performance tests
-
Passes ...