2. OVERVIEW
Definition of Done is a shared understanding of expectations, between
Engineering Team and Product, that must be met in order for feature to be
accepted and released.
It is recommended that once feature is setup, use this list to determine what
all from this list, applies to the concerned feature.
3. DEVELOPMENT CHECKLIST
Code review completed for
• Code structure, format and consistency
• Code comments
• Adheres to security standards and controls
• Appropriate logging and monitoring
• Appropriate error handling and alerting
Code merged in code repository and approval to merge is recorded in
repository
Pipeline executes successfully and code quality check is passed for-
• SonarQube
• Checkmarx
• Twistlock
4. TESTING CHECKLIST
Unit test coded and executes successfully
Functional test documentation and execution completed
User Acceptance Test(UAT) completed
Test automation artifact updated to include code changes and passes
successfully
5. DOCUMENTATION CHECKLIST
High level architecture diagram and documentation updated
Data flow diagram and documentation updated
Process flow diagram and documentation updated
Documentation related to Cloud Suitability Assessment updated
Documentation related to Security Engineering Assessment(SEA) updated
Completed internal documents (application support documents that is used by peers and support
team)
Completed client facing documentation (documentation that support clients)
Completed all documentation as needed by feature story acceptance criteria (for e.g. POC
document, Solution Option Analysis document, Presentation PowerPoint, Visio Diagram)
Service Level Agreement (SLA) document updated
All documents done using standard, pre-approved templates
6. COLLABORATION CHECKLIST
All team members made aware of the feature outcome
Team leadership agrees with feature outcome
Product Owner agrees with feature outcome
Demo to client completed and signoff recorded
All stakeholders (identified in the feature description) agree with feature
outcome, as relevant to their interest
7. SYSTEM OF RECORD CHECKLIST
Archer System updated (if feature work impacts Risk Findings)
JIRA updated (all stories marked complete and hours logged)
Change Management System updated (all Change Request are closed with
implementation date, outcome and results)
Incident and Problem Management process is set and agreed upon with all
stake holders
Service Level Agreement (SLA) updated and agreed upon with all stake
holders
If a spin-off work is realized due to the concerned feature work, new
feature/story is recorded in JIRA backlog, in consultation with Scrum
Master and Product Owner