Mind map template · Technical

Retrospective template, as a mind map

Run your sprint retro on one map the whole team writes on at once: what went well, what did not, what puzzled you, and the actions you carry into the next sprint.

Shiko is in closed beta: this takes you to the wishlist first.

The template as it opens. Every prompt is a node you answer under or replace.

What's inside

Sprint name and dates

  • Check-in
    • How did the sprint feel?
    • Did we meet the sprint goal?
  • Went well ✓
    • A win to celebrate
    • A habit worth keeping
  • Did not go well ✗
    • Something that slowed us down
    • Something that frustrated us
  • Puzzled us ?
    • Something we do not understand yet
  • Thanks
    • Someone who helped us this sprint
  • Themes
  • Actions
    • Improvements for next sprint (a task list)
    • Last sprint's actions (a task list)

How to run it with your team

  1. Check in firstStart with how the sprint felt and whether you met the sprint goal. The Check-in branch has both questions ready.
  2. Everyone writes at the same timeShare the map with a room code. People add what went well, what did not and what puzzled them in parallel, instead of taking turns at a whiteboard.
  3. Group it into themesRead the answers together and name the patterns under Themes. Thanks has its own branch, so good work gets said out loud.
  4. Leave with actionsActions holds two task lists: this sprint's improvements, and last sprint's actions to check off. Give each list an owner and a due date.

What is a sprint retrospective?

A sprint retrospective is the meeting at the end of a sprint where the team looks back at how it worked, not at what it built, and agrees on a few things to change. In Scrum it is the last event of every sprint, after the review, and the Scrum Guide caps it at three hours for a one-month sprint; most teams on two-week sprints need about an hour. Teams that do not use Scrum hold the same kind of meeting after a project or a launch.

A good scrum retrospective feels safe: people talk about the work and the process, not about who to blame. It hears from everyone, not only the loudest voices, and it ends with two or three actions that each have an owner, rather than a long list nobody returns to. The next retro opens by checking whether those actions happened.

A mind map suits a retro because everyone can write at once, the answers sit side by side under each question, and the actions stay on the map for the next sprint. It works as a sprint retrospective template for Scrum teams, and as an agile retrospective template for any team that works in cycles.

When to use it

Hold the sprint retrospective at the end of every sprint, while it is still fresh. The format works for any team that works in cycles, not just software: a marketing campaign, a launch, a term at school.

Retros fail when the actions are forgotten by the next one. A retro template that keeps last sprint’s actions on the same map means you start every retro by checking what actually changed.

Questions

Can my whole team edit it at once?

Yes. Everyone you invite works on the same map live, and you see who is typing where.

Can I export the retro?

Yes. Every map exports to PNG and SVG; Pro adds PDF and JSON.

How long should a retrospective meeting take?

About an hour for a two-week sprint, and up to three hours for a one-month sprint, the limit the Scrum Guide sets. Ten minutes to check in, twenty to write, twenty to talk through the themes, and ten to agree on actions is a good split for an hour. This retrospective meeting template follows that order from top to bottom.

Can we reuse it every sprint?

Yes. Start a fresh copy for each sprint, or keep one map and add a branch per sprint so the history stays in one place.