Q3.2 Retro Discussion
Open
STR
- Dominant language
- Python
- Stars
- 2
- Forks
- 22
- Avg merge
- 2d 35m
- Merged PRs (30d)
- 11
Description
QA - How can we improve QA process?
Improve Ticket Documentation:
- Add content to list Expected Output or other observable change
Workflow - How can we be more sustainable?
- Requirements, Design, API, UI as separate stages?
- How can we have certainty of stages with agility in a fast project?
Action Items:
- Edit Definition of Ready for QA (all code in available TEST, ticket is moved to Ready for QA, ticket must have expected outputs
- Revise Templates for Sub Tasks for API, UI, Design - Include Checklist of items to address, Expected Outputs, Link to Figma (if appropriate)
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.