2023-02-09 13:47:25 +01:00
|
|
|
### Definition of Ready
|
2023-04-03 14:56:37 +02:00
|
|
|
|
2023-01-03 11:32:28 +01:00
|
|
|
- [ ] I am happy with the code
|
|
|
|
|
- [ ] Short description of the feature/issue is added in the pr description
|
|
|
|
|
- [ ] PR is linked to the corresponding user story
|
|
|
|
|
- [ ] Acceptance criteria are met
|
|
|
|
|
- [ ] All open todos and follow ups are defined in a new ticket and justified
|
|
|
|
|
- [ ] Deviations from the acceptance criteria and design are agreed with the PO and documented.
|
|
|
|
|
- [ ] No debug or dead code
|
2023-05-22 09:33:23 +02:00
|
|
|
- [ ] My code has no repetitions
|
2023-01-03 11:32:28 +01:00
|
|
|
- [ ] Critical parts are tested automatically
|
|
|
|
|
- [ ] Where possible E2E tests are implemented
|
|
|
|
|
- [ ] Documentation/examples are up-to-date
|
|
|
|
|
- [ ] All non-functional requirements are met
|
|
|
|
|
- [ ] Functionality of the acceptance criteria is checked manually on the dev system.
|
