Start from the facts
Ask the assistant to summarize the sprint — what shipped, what slipped, and why — so the retro starts grounded in reality rather than memory.
Run retrospectives grounded in what actually happened, with AI summaries of the sprint and action items tracked as tasks.
Sprint recap
Summarize what shipped and slipped.
Discuss
Capture what to keep and change.
Actions
Track improvements as tasks.
Record
Keep a history of retros.
What you can do with Wyatt
Sprint recap
Summarize what shipped and slipped.
Discuss
Capture what to keep and change.
Actions
Track improvements as tasks.
Record
Keep a history of retros.
Ask the assistant to summarize the sprint — what shipped, what slipped, and why — so the retro starts grounded in reality rather than memory.
Capture what went well, what to improve, and what to try, in a structured document the team contributes to.
Create tasks from retro action items so improvements actually happen next sprint.
A history of retros shows whether the team is improving and which changes stuck.
Yes. The assistant can summarize what shipped, what slipped, and why.
In a structured document the team contributes to during the retro.
Yes. Create tasks from retro action items.
Yes. Keep a history to see whether changes stuck.