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

  1. Create a retro for the period or project.
  2. Team members add notes under prompts (What went well / What didn't / Ideas).
  3. Vote to surface top themes.
  4. Group related notes into clusters.
  5. Convert clusters into action items with owners and due dates.
  6. 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