Retrospectives
Running a retrospective
Structured retros with prompts, voting, grouping and action items.
Retrospectives
Run team retros directly in Kudu β no separate whiteboard tool needed.
Flow
- Create a retro for the period or project.
- Team members add notes under prompts (What went well / What didn't / Ideas).
- Vote to surface top themes.
- Group related notes into clusters.
- Convert clusters into action items with owners and due dates.
- Action items link back to the Roadmap or Issues for follow-through.
Best practice
- Keep retros to 45β60 minutes.
- Time-box each phase (add, vote, discuss, decide).
- Review last retro's action items at the start of the next one.
Last updated July 26, 2026
