15 items to include in your Definition of Done (DoD)
When I join a team, one of the most common exercises that I help the team with is the Definition of Done (DoD). Wikipedia defines Definition of Done (DoD) as follows:
“The exit-criteria to determine whether a product backlog item is complete. In many cases the DoD requires that all regression tests should be successful. The definition of “done” may vary from one Scrum team to another, but must be consistent within one team.”
The original page can be reached here.
I like to help the team to come up with their own Definition of Done (DoD), but in the end I like to challenge their DoD, making them think a bit ;)
Below I am listing 15 items that you might or might not want to include on your DoD. Some of these items are more challenging than others, but this is just a basic list of ideas that can help you to define your own DoD, a general guideline; feel free to pick and choose those that best apply to your own situation.
X% of code coverage from Unit Test
Automated tests for the User Story are created and pass
Acceptance criteria is met
All regression testing of the product is passing
System-level Non-Functional requirements ( e.g. System-level performance) tested and passed
Software is running in the The server to be defined by the team (optimally in pre-production)
Code review by peer
Technical documentation updated
User documentation updated
User Documentation is localised
Localisation for the story is done
Localisation testing is done
Marketing input is done
Legal documents are done
Beta Testing is done
If you liked these questions and want to receive other tips, subscribe to the mailing list. I promise to deliver only high-quality content.
Cheers,
Luis
The post 15 items to include in your Definition of Done (DoD) appeared first on Luis Gonçalves - Blog.
