-
-
Notifications
You must be signed in to change notification settings - Fork 1
Definition of Done
Tobias edited this page Jan 9, 2023
·
1 revision
- The code is complete and imported into the versioning system
- The code complies with coding standards and contains no linter errors
- The code complies with the specifically agreed coding guidelines
- The code is tested sufficiently and succesfully
- The code has been peer reviewed or pair programmed.
- All acceptance criteria are met
- The documentation and, if applicable, user manual have been adapted
- The build within the CI/CD pipeline is successful.
- The changes are deployed on the testing environment
If an issue meets the Definition of Done, it must be given the corresponding Status: Completed
label. The issue is now fully processed and can be flagged. The issue can then be closed.
README | Contributing | Code of Conduct | Support | Funding | Security | License |
- Home of the Wiki
- Roadmap
- API Reference
- Glossary
- Contributor Guide
- Code of Conduct
- Support
- Funding
- Security
- License
- Description of Core Essence
- Cost Estimates
- Staffing Estimates
- Predicted Benefits
- Risks
- Scheduled Milestones
- Definition of Ready
- Definition of Done
- Project Decisions
- Technological Decisions
- Sprint Reviews
- Sprint Retrospectives
- Continuous Integration
- Continuous Deployment
- Operations Troubleshooting
- External Systems
- Style Guide
- Specific Views
- View 1
- ...
- About
- Introduction and Goals
- Constraints
- Context
- Solution Strategy
- Building Block View
- Runtime View
- Deployment View
- Cross Cutting Concepts
- Design Decisions
- ADRXX Template
- ...
- Quality Requirements
- Risks and Technical Debt
- Glossary
- Reference Manuals
- Support Guides
- Release Notes