AgileHero

Retrospectives · Included with Pro

Sprint retrospective toolA retro that runs itself.

Pick one of 16 templates and the room walks the team through check-in, writing, grouping, blind voting, discussion and commitments — notes anonymous by default, a shared timer on every stage, and last retro's open actions reviewed first.

Start free Included with Pro · free in every 14-day trial

How a retro runs

1

Pick a template, open the room

Choose one of 16 ready-made formats — Went well / To improve / Ideas, Start / Stop / Continue, 4Ls, Sailboat and more — name it, date it, and the retro is open for notes before the meeting starts.

2

Run the stages

The facilitator walks the room through check-in, review actions, write, group, vote, discuss and commit, each stage on a shared timer everyone sees. Notes are hidden and anonymous until the reveal; votes are blind until the discussion opens.

3

Leave with actions that come back

Committed actions land on the project's Actions list with assignees. The next retro opens by reviewing them — and any action becomes a card on the board when the team decides so, never on its own.

Everything the ceremony needs

16 templates, columns included

Classic, keep-and-change, metaphor and milestone formats — from Went well / To improve / Ideas to Blameless postmortem. Pick one and the columns are set; nothing to configure.

Review actions comes first

Open actions from earlier retros are on screen before anyone writes a new note. The stage the team cannot skip is the one most teams forget.

Anonymous by default, enforced by the server

Other people's notes stay hidden until the reveal, votes are blind, check-in answers only ever appear as a spread — and nobody, facilitator included, can see who wrote a note in an anonymous retro.

Blind, budgeted voting

A per-person budget sized to the number of topics, a cap per topic, totals revealed only when the facilitator opens the discussion. The queue is built from the votes; what the room did not get to waits in a parking lot for the next retro.

A timer on every stage

One shared, server-held clock per stage — pause, add or remove a minute, reset — with sensible defaults so the retro keeps its shape without a stopwatch on the side.

Team health checks

Spotify squad health, a team safety check or the Scrum values: everyone rates 1–5 on their own time, results stay hidden until the check closes, then you see the mean, spread, the two weakest areas and the trend against your last check.

Team health, measured

A health check is a survey, not a meeting. Pick a model — the Spotify squad health check with its eleven dimensions, a team safety check, or the Scrum values — set a closing date, and everyone rates each dimension from 1 to 5 on their own time, with an optional comment. Results stay hidden until the check closes, so early answers do not steer later ones. Then the results page shows the mean, spread and distribution per dimension, the two weakest areas, and the trend against the previous check of the same model — the radar in this loop is the whole team's shape, with last check's outline dashed behind it. Actions written here land on the same Actions list the next retro reviews first.

Why run retros inside the tracker?

Most retro tools compete on template count and icebreakers. The teams that improve need something simpler and harder: the same honest conversation, held regularly, with the actions actually followed up. The tooling problem was never creativity — it's that the retro happens in one tool and the work in another, so actions evaporate on contact with Monday.

AgileHero ships retrospectives inside the tracker as a guided room: a template picked once, stages the facilitator walks the team through, notes anonymous until the reveal, blind voting so the loudest voice does not pick the topics, and a project-wide Actions list that the next retro reviews before anything new is written. Health checks sit in the same module, so how the team feels is measured next to how fast it ships. Improvement becomes a thread you can follow, not a stack of forgotten exports.

What is a sprint retrospective?

A sprint retrospective is the meeting a team holds at the end of each sprint to look at how the work went — not what was built, but how it felt to build it. What went well, what dragged, what should change next sprint. It is the ceremony that makes agile self-correcting: without it, teams repeat the same friction every two weeks and call it process.

A good retro needs surprisingly little: a safe place to write, a way to find out which thoughts the whole team shares, and owners for what changes. That is the shape of AgileHero's retro room — anonymous notes, blind votes to surface the real issues, a shared timer to keep it honest, and an Actions list for what changes, reviewed at the start of the next retro.

Common questions

Are retrospectives free?

Retrospectives and health checks are part of Pro — and fully included in every 14-day trial. Estimation poker, the other ceremony tool, is free on every plan.

Do I need to pick or configure a format?

You pick a template — 16 ready-made ones across four categories — and the columns come with it. Columns are not edited per retro and there is no template editor yet, by design: the catalogue is where a team chooses its format.

How does voting work?

Dot voting, blind: each person gets a budget sized to the number of topics (or a fixed number, or unlimited), with a cap per topic. Nobody sees totals or anyone else's votes until the facilitator moves to the discussion, where the most-voted topics form the queue.

What happens to action items?

Committed actions go to a project-wide Actions list with assignees and a status — open, done or dropped. The next retro opens with a Review actions stage that lists every open action from earlier retros. An action becomes a card on the board only when someone chooses Create card; it never reaches the board on its own.

Are retro notes anonymous?

By default, yes: nobody, including the facilitator, can see who wrote a note, and other people's notes are hidden until the reveal. A retro can be set to optional (authors may add their name) or named, and the level can only ever be raised. Kudos, comments and actions are always named. The server enforces this — hidden notes and voter identities never leave the backend.

What is a team health check?

An async survey on a built-in model — the Spotify squad health check with 11 dimensions, a team safety check, or the Scrum values. Everyone rates each dimension 1–5 on their own time, results stay hidden until the check closes, and the results page shows the mean, spread and distribution per dimension, the two weakest areas, and the trend against the previous check of the same model.

What's the difference between a sprint review and a retrospective?

They look back at the same sprint from different angles. The sprint review is about the product: the team shows what was built to stakeholders and gathers feedback on the work itself. The retrospective is about the team: no stakeholders, just an honest look at how the sprint went and what to change — which is the meeting AgileHero's retro room is built for.

Start with two seats, free forever

Every plan begins as a 14-day trial of every premium module. Set up your first project in minutes.

Try it for free

14-day free trial · no credit card required