Definition of Done

The definition of done (DoD) is a shared understanding within an Agile or Scrum team of when a particular user story satisfies certain specified conditions (acceptance criteria) and is ready to be accepted by a user, internal team, or client stakeholders. Most commonly, we use one or more of the following when defining done.

• Unit tests passed
• Code reviewed
• Acceptance criteria met
• Functional tests passed
• Non-Functional requirements met
• Product Owner accepts the User Story

When addressing a particular stakeholder or agile team member or group, the definition of done might include one of the following, more targeted areas.

Product Owner

• Acceptance criteria has been met

UX

• Business test scenarios to meet all acceptance criteria have been written
• Usability has been validated
• Wiki has been updated (if applicable)
• Story has been tested on a device(s)

Development

• Automated test scripts have been written
• Field level and page level validation errors (front-end and server-side) integrated and functioning
• READMEs, other appropriate docs, APIs fully updated
• Module dependencies are up-to-date and are at the latest resolvable version
• Code refactored for clarity and to remove any known technical debt
• Deployed to the dev environment
• Deployed to the stage environment
• Source code committed
• Unit test coverage of code = 100% (90% required)
• Code reviewed (or developed by pair)
• Security reviewed and reported
• Build process updated
• Feature toggles created
• Source documentation generated
• API documentation generated
• Code quality checks passed
• Load tests passed
• Guides and training draft updated
• Security & privacy gates passed
• Tested in IE 11, Chrome, Safari, etc and iPad