Sprint Retrospective Presentation Template

Sprint retrospectives work best with structure. Without it, they drift into unfocused venting or polite silence. A good retrospective presentation gives the team a container for honest reflection, surfaces the real blockers, and ends with concrete commitments — not just feelings.

The Purpose of a Sprint Retrospective

A retrospective is not a performance review. It is a structured team conversation about process — what worked, what did not, and what to change. The output is not a list of complaints but a small number of specific, owned action items.

Retrospectives fail when they generate fifteen action items nobody is accountable for, when the same issues appear sprint after sprint without resolution, or when the format is so rigid that nothing honest gets said. A clear presentation structure prevents the first two failures; psychological safety prevents the third.

Slide-by-Slide Template

Slide 1: Sprint Summary

Date, sprint number, and a quick data block: planned story points, completed story points, and velocity compared to the prior sprint. Show these numbers without editorializing — the team will draw their own conclusions, and the numbers set a shared baseline.

Slide 2: What We Committed To

The sprint goal and the list of stories that were planned at the start. This is not the place for judgment — just a factual record of what the team intended to accomplish. Seeing the original commitment before the retrospective anchors the conversation in reality rather than memory.

Slide 3: What We Shipped

What actually got done — completed stories, released features, resolved bugs. Include anything that was completed but was not originally planned. Celebrating real output matters: teams that do not regularly acknowledge what they shipped undercount their own contribution.

Slide 4: What Did Not Ship

Carry-over items, dropped stories, and anything that was started but not completed. Note briefly why each item did not finish — scope changed, blocked by dependency, underestimated complexity. This is not blame, it is data. Patterns across multiple sprints are where the real process insights live.

Slide 5: What Went Well

Open this to the team before the presentation — collect sticky notes, anonymous form responses, or Slack comments in the day before the retro. Synthesize themes on this slide. Good themes to watch for: communication that worked well, process improvements that paid off, collaboration that was effective, technical decisions that proved right.

Slide 6: What Could Have Gone Better

Same collection method as the previous slide. Common themes: unclear requirements, blocked dependencies, context switching, testing gaps discovered too late, unclear ownership. The goal is pattern recognition, not fault assignment. One person's problem is usually a system problem.

Slide 7: Process Experiment Review

If the team tried a process change in the last sprint — a new meeting format, a new review process, a new tooling convention — assess it here. Did it work? Keep it, adjust it, or drop it? Many teams skip this review step and end up accumulating process experiments that nobody evaluates.

Slide 8: Action Items

Three or fewer specific, owned, time-bounded commitments coming out of the retrospective. Format for each: what will be done, who owns it, and when it will be complete or reviewed. Action items without owners are wishes. Keep this list short — five action items that nobody does are worse than one that gets done.

Slide 9: Action Item Review From Last Retro

Did the team do what it said it would in the last retrospective? Review each item from the previous session. This accountability step is what separates retrospectives that drive change from retrospectives that generate the same list every sprint.

Facilitation Notes

Do not read the slides aloud — show the data and let the team react. Use the slides as a structure, not a script. If conversation goes deep on one slide, let it. The most valuable retrospective time is often in the unplanned discussion that a good question opens up.

Rotate facilitation. The same person facilitating every retrospective tends to produce the same retrospective every sprint.

Build Your Retrospective Deck With slide-deck.io

slide-deck.io is a free, browser-based presentation tool that engineering teams use for recurring ceremonies — retrospectives, sprint reviews, all-hands — without a subscription or per-user fee. Build once and reuse the template each sprint.