The DoD is usually a short document in the form of a checklist, that defines when a product backlog item (i.e. user story) is considered “done”.

The best check whether something is “done” is to simply ship it!

A typical DoD might look like this example:

• Automated tests are written and all tests are green
• Code is refactored and reviewed
• Code is integrated with master branch
• Deployed to staging environment
• Translated into English and German

DoD is a checklist of what needs to be done to a product backlog item before the team can start implementing it.

Note that the DoR is NOT part of the Scrum Guide — and that is for good reason. The DoR should not be used as a phase gate for Sprint Planning or as a way push away responsibility!

A typical DoR might look like this example:

• PO and Dev Team need to have talked about the story at least once
• Story must have clear business value
• Effort needs to be estimated
• Story must be broken down enough to fit a single sprint
• Story needs at least one acceptance criteria

A user story should be Independent, Negotiable, Valuable, Estimable, Small and Testable.

• What are DoD and DoR in Scrum?