Management Sprint Retro

Purpose

Facilitate structured sprint retrospectives that produce actionable improvements. Collects sprint data for an objective baseline, guides the team through reflection formats matched to their current mood, enforces timeboxed activities for psychological safety, and converts insights into concrete action items with named owners and deadlines.

Retrospectives are the engine of continuous improvement in agile teams. Without structure, they devolve into venting sessions or shallow praise that changes nothing in the next sprint. This skill provides a complete, repeatable framework: gather objective sprint metrics before the meeting, select a retro format aligned to the team's emotional state, enforce strict timeboxes that keep the meeting productive, and convert discussion into a maximum of three actionable improvements per sprint with clear accountability. The output is not just a feel-good exercise — it is a prioritized process improvement backlog with owners and deadlines.

The most important rule is that retro output must change behavior. An action item without a named owner and a specific deadline is just a wish. An action item that is too vague to verify will not be done. The three-action-item limit is backed by research on team throughput: teams that commit to fewer improvements reliably complete more of them sprint over sprint.

Agent Protocol

Trigger

"sprint retro", "sprint retrospective", "retro", "retrospective", "sprint review", "what went well", "sprint improvement", "agile retro", "retro format"

Input Context

• Sprint dates, duration, team member names and roles
• Sprint metrics: velocity (points/story count), completed vs committed %, bug count by severity, cycle time distribution (P50/P95), deployment frequency, rollback count, incident count
• Previous retro action items with status: done, in progress, blocked, not started