slide-deck.io

Sprint Retrospective

Agile sprint retro covering velocity, what went well, improvements, and action items.

A complete 8-slide sample deck. The companies and figures in it are invented — slide-deck.io writes the same structure around your own topic, your brand colours and your data, and exports it as an editable .pptx.

Use this template
  1. Sprint 34 retrospective
    1

    Set the norm in one sentence: we discuss systems and decisions, not individuals. Then get off this slide quickly.

  2. The sprint by the numbers
    2

    The numbers set context, they are not the retro. Spend two minutes here at most.

  3. Velocity is steady; unplanned work is not
    3

    Unplanned work tripled over five sprints while completion held flat. That trade is the real topic of this retro.

  4. What went well, what did not
    4

    Read both columns fully before opening discussion. Retros that start with the problems never get back to the wins.

  5. What we are hearing underneath the items
    5

    This is the slide that makes a retro useful. Four symptoms, four systems — none of them a person.

  6. What we tried last sprint and whether it worked
    6

    Always audit the last retro’s experiments. Skipping this is how teams generate the same actions every two weeks.

  7. What we will change next sprint
    7

    Four changes is the ceiling. Each has a named owner and an observable outcome, which is what makes the next retro possible.

  8. Carried into next sprint
    8

    Say explicitly that carry-over is not failure. Naming it plainly is what stops teams from padding estimates to hide it.

Build this deck around your own material.

Get started free