MS
Maya Engineer
Twice this sprint, work sat overnight waiting for review.
Retrospective
Talk through the sprint. Leave with one change the team owns.
Specific observations become visible themes, shared priorities, and small improvement commitments without turning the retro into a form.
Just talk. BigWow keeps up. No special commands or constant note-taking. Have the conversation you were already going to have.
From two handoff examples Theme · needs team choice
Late review handoffs Improvement theme Two concrete examples attached
AL
Ari Team lead
“Let’s try pairing on risky changes next sprint. Maya will run it; we’ll review the results at retro.”
Pairing trial Confirmed by Ari ✓
Team experiment ✓
Pairing trial Improvement action Pair on risky changes Maya · Next sprint
Check-in Review trial results Ari · Retro in two weeks
From two handoff examples→Confirmed by Ari
How the template helps
Reflection that ends in a small, owned experiment.
Start, Stop, and Continue observations stay distinct before the team chooses what to change.
What the team leaves with
A retro commitment that will not disappear into notes.
The selected improvement remains attached to the evidence, owner, and review date.
Run a retrospectivePhoenix · Sprint 18 Retrospective record
Commitment confirmedConfirmed outcome Trial pairing on risky changes
Chosen to reduce overnight review handoffs
Improvement action Confirmed
Pair on risky changes Maya · Next sprint
Linked to two late-review observationsCheck-in Confirmed
Review trial results Ari · Retro in two weeks
Success question attached