Since a Sprint moves at a rapid pace, the team needs a artifact of what needs to be done to a story to call it done. They write down all the typical things they do and that artifact is called DOD or Definition of Done.
There are at least three types of Definitions of Done.
Here is an example DOD for a software team
What must happen for the story to be marked as complete.
An example Story definition of done would look like this.
- All stories should have automated acceptance test.
- The story should have working code supported by unit test that provide around 60 – 70 percent coverage.
- The story should have well defined acceptance criteria.
- The code must have been written as a pair or should be code reviewed.
- Code must be completely checked in to the source control system and the build should pass with all the automated tests running.
- The product owner must accept the story.
- Product owner should have defined a sprint goal.
- All stories completed in the sprint must be accepted by the product owner
- All the automated acceptance tests should be running for the stories in the sprint.
- All code should have been pair programmed or must have gone thorough a code review process.
- If there is a database involved, the database scripts must have been automated and tested.
- Product is deployed to the test box and makes it to staging
- Product has a formal release date.
- There are deployment documents for the release
- Training manuals are available for users.
- All stories for the release are completed and accepted.
- The release does not have any level one bugs.