| README.md | ||
A DoD that we can all use
What is a DOD
A DoD (Definition of Done) is a list of items that need to be fulfilled in order to consider a feature or story to be complete. It is a minimum list, so you can have more specific DoDs for specific features.
Why is it important
By having a common DoD we can all make sure that features that we are working on, that we think are complete, actually are. This way we can avoid miscommunication and duplication of work.
How to use a DoD
The DoD should be a list of items that every feature or story needs to be completed. It should be used by the team to verify a feature or story is ready for release.
Creating a DoD
To create a DoD, you should start with some basics, then add items that are important to your team, and refine your DoD over time.
Start with the basics
To start a DoD, start with a set of basic items that are applicable to most teams:
- Code is tested
- All necessary checks have run
- Code is reviewed
- Code is checked in
- Code is deployed
Add items
You might have other items that are important to your team, such as:
- Code is documented
Refine
As you use your DoD, you may find there are items on the list that don’t need to be there. Make sure your team is comfortable with the DoD.
Using the DoD
Once you have a DoD, you can use it to verify that a feature or story is ready for release.
A DoD that we can all use
What is a DOD
A DoD (Definition of Done) is a list of items that need to be fulfilled in order to consider a feature or story to be complete. It is a minimum list, so you can have more specific DoDs for specific features.
Add your own DoD
You can add your own DoD in the issues or via a pull request.