2.1 KiB
Organizations Definition of Done
-
All acceptance criteria from the user story is met
-
UI across all components has a similar look and feel
-
For client-facing work, design ‘OK’ has been given to make sure it not only looks good, but that it follows design standards
-
Error messaging that faces an external customer is friendly, indicates next step they should take, and reveals no system details
-
Error messaging that faces an internal customer indicates as much system detail as necessary to help them locate the problem
-
Error trapping and logging is clear for support team (crashes would result in logging that can be traced to offending code areas)
-
Tests that cover added or modified features have been have been created and/or updated
-
Release notes have been created and are ready for internal users (when changes affect system interactions)
-
Wiki and/or README has been updated (when architectural, structural or feature additions will affect future developers)
-
FAQs have been updated (where feature changes could trigger support tickets that would result only in information passing)
-
Pull request exists (pull request contains description of what the branch is doing, why it’s doing it, and contains a link to the Jira story, screen shots for UI elements, and should annotate any applicable configuration file changes)
-
Smoke, boundary, and exception testing has been completed (in the test environment)
-
Peer review has been completed, including checking adherence to this document (check that release notes, wiki, README, and FAQ have been updated). Minimal peer review requires signoff by two persons other than the original developer.
-
BA has given sign-off that acceptance criteria have been met
-
Code Testing
- Functional passing
- Unit passing
- Load tests
- Performance tests
- Security/penetration tests
- Integration tests
- UAT passing
-
Code Review
-
Release
-
Deploy
-
Training Material
-
Documentation
-
Communications
-
International Law
- GDPR
- ...?
-
Design Approved
-
0 bugs