Free tool · No signup

Retro Template,
In One Click.

Pick a retrospective format. Copy a ready-made markdown template. Paste it into Notion, Confluence, Google Docs or your team channel.

Pick a format

Sprint details (optional)

Team name
Sprint number
Date

Your template

Loading template...

Run retros without copy-paste

SprintFlint pulls completed tickets, blockers and velocity into the retro automatically. Your team focuses on the conversation, not preparing the doc.

Start Free

Sprint retrospective FAQ

How long should a sprint retrospective be?

For a two-week sprint, plan 60-90 minutes. Use a hard timebox per section so you don't over-run on the first bucket. Keep facilitation tight; the value is in the actions, not the venting.

How many action items per retro?

One to three. More than that and nothing gets followed through. Assign an owner and a due date to each. If you can't, drop it.

Which retro format should I use?

Start/Stop/Continue if your team is new to retros. Mad/Sad/Glad after a hard sprint. 4Ls for deeper learning sprints. Sailboat for distributed teams on a visual board. Rotate every few sprints to keep the format fresh.

Should the manager run the retro?

Generally no. Rotate facilitation across the team so people feel safer surfacing issues. The manager is a participant, not the chair.