Retro Runner - Guided Team Retrospectives by Angelica Berryhill
Run your team's first retrospective without guesswork. Six session formats, a timer that keeps the shape of the hour, and questions with examples from your own industry. Everything stays on your device. No account, no network, no tracking.
Extension Metadata
About this extension
Retro Runner walks you through running a retrospective with your team — a short, regular
meeting where the team reviews how it worked, not what it produced.
It is built for managers who have never run one. You pick how long you have, and the tool sets
out the shape of the session, tells you what to ask, says what a useful answer sounds like, and
keeps time. You finish with one change the team has agreed, with a name against it and a date.
WHAT IT DOES
• Six session formats, from a twenty-minute round-the-room to a full ninety-minute timeline of
a finished project. "Your first retrospective" spends real time explaining what is about to
happen and deliberately ends with a single change rather than a list.
• Every question comes with an example from your own industry. Choose healthcare, logistics,
manufacturing and food production, professional services, property and construction,
education, hospitality and events, or non-profit and public sector, and the examples change
with it. There are a hundred and sixty of them, and not one mentions software.
• A timer that keeps the shape of the session without hurrying anyone. Nothing advances by
itself. When a phase overruns, the time comes off the discussion and never off the part where
the team agrees what to change — running out of time before deciding anything is the most
common way a first retrospective fails.
• The next session opens by asking whether the last change actually happened. That is what
turns a series of meetings into progress.
• Copy any session out as plain text to paste into an email or your notes.
WHAT IT DOES NOT DO
There is no account, no sign-in and no server. Retro Runner makes no network requests of any
kind. Everything your team says stays in this browser, on this device, and there is a working
delete for a single session and for everything at once.
It asks for one permission — storage — and nothing else. It cannot read the pages you visit,
because it has no way to.
ABOUT THE APPROACH
The practice is described in the Scrum Guide (2020), which sets the Sprint Retrospective at a
maximum of three hours for a one-month Sprint. The questions, the formats and every industry
example here were written for this tool; nothing is reproduced from the Scrum Guide or the
Agile Manifesto, both of which are credited in the About panel.
Published by Influential Agile Leader. Free, with nothing to upgrade to.
Not affiliated with, endorsed by, or sponsored by Scrum.org, Scrum Alliance, or the authors of
the Scrum Guide.
meeting where the team reviews how it worked, not what it produced.
It is built for managers who have never run one. You pick how long you have, and the tool sets
out the shape of the session, tells you what to ask, says what a useful answer sounds like, and
keeps time. You finish with one change the team has agreed, with a name against it and a date.
WHAT IT DOES
• Six session formats, from a twenty-minute round-the-room to a full ninety-minute timeline of
a finished project. "Your first retrospective" spends real time explaining what is about to
happen and deliberately ends with a single change rather than a list.
• Every question comes with an example from your own industry. Choose healthcare, logistics,
manufacturing and food production, professional services, property and construction,
education, hospitality and events, or non-profit and public sector, and the examples change
with it. There are a hundred and sixty of them, and not one mentions software.
• A timer that keeps the shape of the session without hurrying anyone. Nothing advances by
itself. When a phase overruns, the time comes off the discussion and never off the part where
the team agrees what to change — running out of time before deciding anything is the most
common way a first retrospective fails.
• The next session opens by asking whether the last change actually happened. That is what
turns a series of meetings into progress.
• Copy any session out as plain text to paste into an email or your notes.
WHAT IT DOES NOT DO
There is no account, no sign-in and no server. Retro Runner makes no network requests of any
kind. Everything your team says stays in this browser, on this device, and there is a working
delete for a single session and for everything at once.
It asks for one permission — storage — and nothing else. It cannot read the pages you visit,
because it has no way to.
ABOUT THE APPROACH
The practice is described in the Scrum Guide (2020), which sets the Sprint Retrospective at a
maximum of three hours for a one-month Sprint. The questions, the formats and every industry
example here were written for this tool; nothing is reproduced from the Scrum Guide or the
Agile Manifesto, both of which are credited in the About panel.
Published by Influential Agile Leader. Free, with nothing to upgrade to.
Not affiliated with, endorsed by, or sponsored by Scrum.org, Scrum Alliance, or the authors of
the Scrum Guide.
Rated 0 by 0 reviewers
Permissions and data
More information
- Add-on Links
- Version
- 1.0.0
- Size
- 97.02 KB
- Last updated
- 19 days ago (Sep 4, 2026)
- Related Categories
- License
- All Rights Reserved
- Privacy Policy
- Read the privacy policy for this add-on
- Version History
- Add to collection