Sprint Retrospective
A sprint retrospective is a recurring meeting (typically 30–60 minutes at the end of each sprint) where the team reflects on what went well, what didn't, and what to change in the next sprint. It is one of the five Scrum events defined in the Scrum Guide and is used more broadly in agile and non-agile teams.
Key Points
The goal is actionable improvement — each retro should produce 1–3 specific changes the team will implement next sprint
Common frameworks: Start/Stop/Continue, Mad/Sad/Glad, 4Ls (Liked, Learned, Lacked, Longed for)
Action items from retros must be tracked — untracked action items have near-zero completion rates
The facilitator should rotate each sprint to prevent one person from dominating the format
How Vizually.AI Uses This
On a Vizually.AI canvas, create a dedicated "Retro Actions" zone. After each retrospective, add action item cards with assignees and deadlines. Draw depends-on connectors from action cards to the next sprint's milestone card. The AI Health Check flags retro action items that are still open when the next retrospective arrives.