Definition of done

Definition of done

Putting a DoD on paper is simple. The difficulty often lies in having the development team actually respect the contract. So what can a team do to ensure that the DoD and acceptance criteria are respected? Start by embedding them in the team’s natural workflow.

Definitions of done correspond to different parts of the development process: technical tasks, user stories, and bugs.

Good development practises

1. Code changes need to be checked into the version control system
2. Tests (unit and integration) that run as part of the build are created or updated for all new code and code that may have been impacted by changes
3. Delete branches after merging code
4. Data that gets sent back to clients is documented
5. No known critical defects are left in the code
6. Meets Architectural Guidelines
7. Code builds without warnings (technical task)
8. Sonarcube does not introduce any new code smells and Sonarcube build passes
9. Integration test suites are passing

Maintaining paperwork

1. Documentation written/updated and details about it are mentioned in the Jira story.
2. Stories satisfy acceptance criteria before being closed.
3. Ticket is updated with any info relevant to the change and any decisions made
4. Feature is pushed to Production
5. Build pushed to demo server and the feature has been signed off by PO (demoed)
6. If Production code gets deployed but the code is not active, follow up story is created
7. Successfully tested in the highest deployed environment (no major or medium level bugs)