What is the Definition of Done (DoD)?
Definition of Done (DoD) is the list of activities that are required to deliver the Product Backlog Items (PBI) in the desired quality and the steps required for the team to accept a job as complete. The goal of Sprint in Scrum is to produce software deliveries ready to go live. In this sense, DoD should determine the standard actions required to produce the finished software ready to go live.
For example, a standard DoD sample can be found below:
| DOD Steps | Control |
| Analysis | Yes |
| Design | Yes |
| Coding | Yes |
| Code Review | Yes |
| Functional Test | Yes |
| KKT | No |
| Documentation | No |
A general Definition of Done as per above is a general quality criterion for all PBIs, but a separate Definition of Done can be defined for a specific PBI where necessary. For example, an additional Stress Test step can be added to an online system PBI in addition to the above general definition, creating a custom DoD for the specific request.
The simple DoD we see in the above example should be detailed by the team and general standards should be defined for each step. Take the coding step, for example. What is coding for our team? Which coding standards and practices do we follow? Are we going to refactor our code during the coding period and to what extent? The answer to these and similar questions should be clear, transparent and thus have a certain quality standard.
DoD is a very important concept that must be unconditionally adhered to for quality and transparency. Within the process, the team should go over the scope of the DoD and develop it, thus triggering its productivity. Don’t forget that quality is the responsibility of the Development Team.
