Retro 29.1/ Q1.1 Improve Requirement Clarity & Ticket Definition
Open
STR
- Dominant language
- Python
- Stars
- 2
- Forks
- 22
- Avg merge
- 2d 35m
- Merged PRs (30d)
- 11
Description
**Description:**
Requirements during the sprint were unclear and changed during development and QA, leading to rework. Improve clarity by defining stable acceptance criteria upfront and ensuring ticket descriptions focus on the problem rather than prescribing solutions.
**Acceptance Criteria:**
- [ ] Acceptance criteria defined and agreed before development starts
- [ ] Ticket descriptions clearly state the problem
- [ ] Reduced requirement changes during implementation and QA
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.