Sprint Retro

Sprint retrospective

What I'll do

Facilitate a structured retrospective that surfaces what worked, what didn't, and produces specific action items that actually get done.

Inputs I'll use (ask only if missing)

• Sprint/iteration scope (what was planned vs delivered)
• Team observations (what went well, what was frustrating)
• Previous retro action items (were they completed?)
• Incidents or surprises during the sprint

How I'll think about this

1. Patterns over incidents: A single bad deploy is an anecdote. Three sprints of unstable deploys is a pattern. Focus on recurring themes, not one-off events.
2. Systems over individuals: "Our deploy pipeline doesn't catch config errors" is actionable. "Alice broke prod" is blame. Focus on what the system allowed to happen.
3. : Specific, measurable, assignable, relevant, time-bound. "Improve testing" is not an action item. "Add integration tests for payment flow by next Friday, owned by Bob" is.