- Have we written acceptance criteria written in Given, When, Then Format (Gherkin)?
- Have UX designs been added and signed off as required?
- Is the technical design agreed?
- Has the story been estimated by the development team?
- Is the ticket [user story] broken down into its smallest deliverable component that still delivers value to the user?
- Are any Dependencies (internal or external) identified that would block the user story from being completed in the sprint?
- Have any relevant Non-functional requirements defined (Page performance, Performance under load, logging, alert metrics etc)?
- Is the testing scope agreed - Unit, Integration, E2E, Manual?
- Are there any specific testing requirements (Test Data, Environment requirements)?
- Has the ticket been reviewed and approved by client?
Applies to all work items (user stories, enhancements, bugs, etc.)
- Code Quality: The code meets all predefined coding standards and practices.
- Code Review: The code has been thoroughly reviewed by at least one other team member.
- Unit Testing: All new or modified code is covered by unit tests with a predefined code coverage percentage met or exceeded.
- Integration Testing: Changes are tested in an integrated environment to ensure they work with existing systems.
- Documentation: Any changes to the system or API are documented appropriately.
- Security: All changes are checked for security vulnerabilities.
- Performance: Changes do not degrade system performance based on predefined benchmarks.
- Have all acceptance criteria been met?
- Functional Testing: Has the feature has gone through functional testing to validate that it meets the user requirements?
- User Documentation: Has relevant user documentation has been updated or created?
- Has item passed through client acceptance prior to deployment
- Deployment Plan: Has a detailed deployment plan been created and reviewed when appropriate
- Release Notes: Release notes are prepared and include new features, enhancements, and bug fixes.
- Customer/Product Owner Feedback: Feedback from the customer or product owner has been received and incorporated.
- Retrospective Improvements: Any improvements identified during retrospectives related to the definition of done are embraced and implemented.