Skip to content

Template · every two weeks

A sprint review with the numbers already in

Eight slides for the end of every sprint: whether you met the goal, the evidence, a demo of what shipped and what moves to the next sprint. Read what's done from your tracker instead of counting tickets by hand, and start the next sprint's deck in one click.

Use this template See every slide

Free during early access. Sign up with your email, and the template opens in your workspace in your own brand.

The first slide of the sprint review template, in a made-up brand: Sprint review, Sprint 12, and a blank for the sprint goal, met or missed.

The template as Cue draws it, in a made-up brand kit. Blanks in brackets are yours to fill, by hand or from a brief.

When to use it

For the end of every sprint, when the team shows what it shipped

A sprint review answers one question first: did we meet the sprint goal? Everything after is the evidence: the numbers, the work you can demo, what slipped and why, and what carries over. It happens every two weeks, so rebuilding the deck by hand, counting tickets and pasting charts, adds up fast.

This template keeps to that order: the goal, met or missed, the sprint in numbers, velocity over the last six sprints, a demo of what shipped, plan vs actual, carry-over, the retro and next sprint's goal. Each slide has a presenter note, and the deck takes about ten minutes to present.

Reporting to the business every week, or to a board every quarter? There are templates for those too.

How it works in Cue

Set it up once. Every sprint after is one click.

  1. Start this sprint's deck

    Pick the template and name the sprint. Paste the sprint goal and a few notes as a brief if you like, and Cue's AI fills in the blanks, reading your connected tools where you point it to them.

  2. Read the sprint from your tracker

    Connect Jira, Linear or GitHub. Jira comes with ready-made sources: the issues done this sprint, and the open sprint's issues counted by status, for a chart. Or bind the slides to a sheet your tracker exports.

  3. Demo it live

    Present from your phone while the team follows along on their own screens, in their own language. Product demo slides show the feature without leaving the deck.

  4. Next sprint, one click

    Start next review copies the deck, reads every bound number again, writes a What changed slide and flags any slide whose story the new numbers no longer support.

Every sprint is kept in a series with its date, presenter and key numbers, and you can share any of them as a link or a PDF.

What's in the deck

Every slide, and how to present it

8 slides, about 10 minutes when you present it.

  1. Opening · 30 sec

    The sprint goal, as a claim: met or missed

    Team · date · presenter

    Presenter note: Say whether we met the sprint goal in the first sentence. Everything after is the evidence.

  2. Key numbers · 1 min

    What the numbers say about this sprint

    Issues committed · Issues done · Sprint goal completion · Bugs closed

    Presenter note: Bind these to your tracker's export (ask Cue: bind slide 2 to the sheet). Name the gap between committed and done before anyone asks.

  3. Bar chart · 1 min

    Velocity, last 6 sprints

    6 bars, S7 to S12

    Presenter note: These bars are sample values: bind them to the last 6 rows of your velocity sheet. Explain the dip or the jump, not the average.

  4. Points · one click each · 3 min

    What we shipped

    Feature · Feature · Fix

    Presenter note: Demo each one live if you can. One click per item; the person who built it says one sentence.

  5. Side by side · 1 min

    What slipped, and why

    Planned · Shipped

    Presenter note: Be specific about the cause: scope, an estimate, a dependency or an interruption.

  6. Table · 1 min

    What moves to the next sprint

    Columns: Item, Owner, Why it moved, New date

    Presenter note: Every row needs an owner and a date, or it isn't carried over: it's dropped.

  7. Points · one click each · 1.5 min

    What we'll change next sprint

    Keep · Stop · Try

  8. Closing · 1 min

    Next sprint's goal

    The one thing we need from stakeholders to hit it

    Presenter note: End on the ask. If there's nothing to ask, say the goal again and give the time back.

Questions

About this template

More in all questions.

Is the template free?

Yes. Every feature in Cue is free during early access, templates included. Later, the Free plan holds up to 3 decks; Team has unlimited decks, live data and Start next review.

Which trackers can it read?

Jira and Confluence, Linear and GitHub, each through your own account, and Cue only ever calls their tools that read. You can also bind slides to a Google Sheet, a CSV file or a JSON URL.

Can I change the slides?

Yes. Ask Cue for a change in plain words ("add a slide for the bugs we closed", "split the demo into two slides"), or edit the text and the slide order yourself. The layouts follow your brand kit, so the deck stays on brand however it's edited.

Can I run it from Claude or ChatGPT?

Yes. Connect Cue's MCP server to Claude, ChatGPT or Cursor, and ask it to start the next sprint review, bind a slide to your data or rewrite a slide. Every change it makes is a version you can restore.

Run your next sprint review in Cue

Sign up with your email and the sprint review opens in your workspace. Free during early access.

Use this template