Loading...
Posted date
The definition of “Done”
Table of contents
- Purpose
- About the definition of “Done”
- Samples
- Licensing
- Sample of definitions of “Done” (Project A)
- Done
- Sample of definitions of “Done” (Project B)
- Done (items completed in each sprint)
- Undone (items that are not completed in each sprint)
- Sample of definitions of “Done” (Project C)
- Done (items completed in each sprint)
- Undone (items that are not completed in each sprint)
Purpose
- To clearly define the delivery conditions of a product or task and to ensure the transparency of deliverables.
- To share delivery conditions among the team and prevent variance in quality between team members.
About the definition of “Done”
- The definition of “Done” indicates what creators need to do in order to release a product.
(These differ from the acceptance criteria set for delivery to the product owner.) - Tasks are grouped into two categories: “Done” and “Undone”.
- Tasks that can be done in the current sprint are classified as “Done” and those that will be difficult to do in the current sprint, such as security testing or load testing, are classified as “Undone”.
- “Undone” tasks are performed as stories (tasks classified as “Done” are not indicated in stories).
- The team must work to reduce the “Undone” tasks, as it is risky to have too many tasks that are “Undone”.
Samples
Licensing
These documents are provided under the Creative Commons Attribution-ShareAlike 4.0 license.
