Retro 29.2 Manage Retro Outputs Effectively
Open
STR
- Dominant language
- Python
- Stars
- 2
- Forks
- 22
- Avg merge
- 2d 35m
- Merged PRs (30d)
- 11
Description
Description:
Retro action items are turning into an unmanaged “idea backlog” with limited follow-through. We need a structured way to track, prioritize, and close them.
Next Steps:
- [x] Limit retro action items to 1–2 per sprint
- [x] Assign a clear owner for each action item
- [x] Track them on the zenhub board for visibility
- [ ] Review progress in stand-ups or mid-sprint check-ins
- [ ] Set up a dedicated session to review past retro items, close irrelevant ones, and prioritize the remaining
- [ ] Revisit and close items in the following retro
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.