Plinkwise Mobile Team, Sprint 14 Retrospective
Sprint retrospective presentation: what changes next
A sprint retrospective presentation has to turn a sprint's facts into a few changes the team will actually make, each with an owner, so the next sprint is measurably different. The mobile team at Plinkwise, an invented budgeting app, committed 34 points and finished 29, traces the gap to one oversized story, and leaves with four actions and a sprint 15 goal.
Every slide, in order
The whole deck as it renders, one slide after another. Read it the way the audience would.
The structure
What each slide is doing, so you can reuse the order even with different content.
- Slide 1cover
- Names the sprint and the one line result, so the retro starts from facts.
- Slide 2metrics
- Committed against completed points, the first fact every retro checks.
- Slide 3metrics
- Cycle time for each completed story, which shows where the sprint actually went.
- Slide 4framework
- Keep, stop and start, agreed by the team, which is the heart of the retro.
- Slide 5timeline
- The action items with an owner, a due date and how the team will know it worked.
- Slide 6comparison
- Sprint 14 beside sprint 13, so one sprint is read as a trend and not a verdict.
- Slide 7takeaway
- Three things the team learned, in its own words, to take into planning.
- Slide 8closing
- Closes with the sprint 15 goal, so the retro hands straight into planning.
Slide by slide
Slide one gives the sprint in one line. Slide two shows committed, completed and carried over points. Slide three charts cycle time for the seven stories that shipped. Slide four is keep, stop and start from the team's sticky note vote. Slide five is the action table. Slide six compares sprint 13 and sprint 14 on four measures. Slide seven lists the three lessons the team voted highest: big stories hide risk, simulators are not phones, and pairing paid off. Slide eight sets the sprint 15 goal, with 30 points committed and no story above five.
How to adapt this deck
A team that does not estimate in points should replace slides two and six with stories committed and completed, and keep the cycle time chart, which works without estimates. A retro after a difficult sprint, such as one with an outage, should add a slide of the timeline before keep, stop and start so the discussion stays on facts. For a quarterly retrospective across several sprints, swap the bar chart for a line of completed points per sprint and keep the action table exactly as it is.
What agile guidance says
The Scrum Guide describes the sprint retrospective as the event that plans ways to increase quality and effectiveness: the team inspects how the sprint went across people, processes and tools, identifies the most helpful changes, and may add them to the next sprint backlog. Atlassian's team playbook frames a retrospective around celebrating what went well, discussing what did not, and deciding how to improve the next sprint. This deck follows both, then makes the changes testable.
What makes this deck work
The gap has a cause on the chart
Slide two shows 29 of 34 points done and 5 carried over. The bar chart on slide three shows where they went: offline transactions took nine working days against a median of three, and the two carried stories were blocked behind it. The team discusses one story, not a vague feeling that the sprint was slow.
Every action has a test
The table on slide five gives each of the four actions an owner, a date and a done when column, such as no story above five points at planning, or median review wait under one day. At the next retro the team can check each one with a yes or no.
One sprint is read beside another
Slide six puts sprint 13 beside sprint 14: 28 of 30 points against 29 of 34, a 2.5 day median cycle against 3. Delivery held up and predictability fell, which is a calmer and more accurate conclusion than one sprint on its own would give.
Questions people ask
What should a sprint retrospective presentation include?
The sprint's facts, committed against completed work and cycle time, then what to keep, stop and start, a short list of owned actions, a comparison with the previous sprint and the next sprint goal. Eight slides is plenty. Most of the meeting should be discussion, with the slides there to anchor it.
Should a retrospective use slides at all?
A few, to put the facts in front of everyone before opinions start. Points, cycle time and last sprint's actions are easier to discuss on a screen than from memory. The keep, stop and start ideas usually come from sticky notes or a board and are added to the deck after voting.
How many action items should come out of a retro?
Two to four. More than that and few get done before the next retro. Give each one an owner, a due date and a way to tell it worked, then review them at the start of the next retrospective so the team sees its changes have consequences.
Why show cycle time in a sprint retrospective?
Because it shows where time went story by story, which points alone cannot. One story far above the median, like the nine day offline story here, usually explains a missed commitment and leads straight to a concrete change, such as splitting large stories before planning.
What is the difference between a sprint review and a retrospective?
A sprint review looks at the product: what was built and what stakeholders think of it. A retrospective looks at how the team worked: process, tools and collaboration. Keep them separate so the retro can be candid without stakeholders in the room.
Can I reuse this retro deck for every sprint?
Yes. Keep the slide order and replace the numbers and stories each sprint. To keep a copy of each sprint inside one deck, use Duplicate slide in the slide rail before editing, since there is no duplicate deck action. Version history also lets you look back at earlier sprints.
Build your own in about a minute
The button below opens the generator with this use case already described. Change the wording to match your own, generate, then edit anything you like.
Make one like thisOther presentation examples
Department update presentation for an all hands slot
A department update presentation has to tell the rest of the company, in a ten minute slot, how the team performed, what it is working on next and what it needs from everyone else. The customer support team at Crewlantern, an invented onboarding software company, reports April in six numbers, shows how reply times recovered after a product launch, welcomes two new people and ends on one ask.
OKR presentation example: objectives, key results, owners
An OKR presentation has to prove to the team and its manager that the quarter has a few ambitious objectives, each measured by numbers with a start point, a target and one owner. The Get Paid team at Pennaway, an invented invoicing app for tradespeople, scores last quarter at 0.72, then sets three objectives and nine key results for Q1 2027.
Project status report presentation example in 8 slides
A project status report presentation has to show, in the few minutes a leadership meeting gives it, whether the project is on schedule, budget and scope, what changed since the last report, and what the leaders need to do. Palletgrove Distribution, an invented wholesaler, reports week 22 of a 39 week warehouse system rollout: amber overall, one site two weeks late, and four asks.
Want the steps in the builder? Read Add charts, maps and diagrams to slides, then Edit your deck with the AI assistant. For everything this generator can do, see the presentation maker.
Sources
Written and checked by the OneCraft team. Last checked .