Work with the right team

This means including everyone who should have a say on how to define “done” for the project: product owners, the Scrum master, Scrum team members, testers, product managers, sponsors, and other relevant stakeholders. 

Establish the criteria

The criteria must be specific, measurable, attainable, relevant, and time-bound. If something on a DoD doesn't apply it's OK to consider it not applicable (N/A).

1. The increment is working and all AC have been met.
2. No Compile Warnings.
3. The deployment pipeline (CI/CD) has been tested and works as expected.
4. The build is stable, and no build errors are present.
5. All code thoroughly tested via unit, integration, and end-to-end tests (? %).
6. The code has been peer-reviewed and approved via pull requests.
7. The increment is thoroughly tested in UI, also against the AC of all the PBIs included in the increment. 
8. All the found defects are fixed and re-tested or documented.
9. Regression testing has been performed, ensuring no critical issues in existing functionality.
10. Performance and security checks are completed and meet the required thresholds (if applicable).
11. All documentation is written and updated (release notes, user guides, support guide, support knowladge base, if applicable).
12. The increment is technical debt free or it is documented.
13. PBIs' statuses are updated.
14. Changes are deployed to the staging environment or OBR file is provided for further validation by PO and QA manager.
15. The feature/demo has been showcased to stakeholders during sprint reviews (if applicable).
16. The increment has been deployed to a staging environment and tested by the team.