> For the complete documentation index, see [llms.txt](https://ploegert.gitbook.io/til/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ploegert.gitbook.io/til/general/agile-development/definition-of-done-dod.md).
# Definition of Done (DOD)
## Feature:
What is the definition of done for Features?
### Scope
* UX considerations (If applicable) are created under parent EPIC
* Sub-Features contain Acceptance Criteria and Test Cases
* Scope changes and design decisions are documented and approved by Product Owner
* Considered DFS requirements in Implementation
* Followed architectural standards around best practices, logging, etc
### Development
* PBIs and Tasks are created to capture Architecture and Design details for Parent Feature
* Code follows appropriate coding standards
* Source control built without errors
* All Tasks for all PBIs have been completed
### Test
* Test plans are updated, executed and passed against QA build
* Severity 1 & 2 Defects are resolved
### Review
* QA Lead confirms that Feature is integrated and passes all Tests
* UX Lead approves Feature meets UI/UX objectives Product Owner or Business Analyst approves that
## Work Item: Definition of Done
What is the definition of done for PBI/Work Items?
* Code is competed with no significant defects
* Code is peer reviewed
* Unit tests are done
* Integration tests are completed
* Regression tests are completed
* Development (PR Commit) Linked to PBI
* Documentation is completed
* Code is moved to QA
* The test results match the acceptance criteria
* CI/CD automation is in place All tasks are marked as done
