Retrospective Template - Free Download & Facilitation Guide
Run effective agile retrospectives with this free template. Includes Start/Stop/Continue, 4L method, Sailboat format and action plan tracking for continuous improvement.
A retrospective is the recurring moment where a team reflects on the past sprint or iteration and formulates concrete improvement actions. Without structure these sessions quickly devolve into aimless complaining or superficial head-nodding. This template provides a proven setup that guides the team through four phases: gauge the mood, collect observations, analyse patterns and record action items. By using the same framework at every retrospective the team builds a rhythm of reflection and improvement that delivers results sprint after sprint. The template includes multiple facilitation formats to keep sessions varied and engaging, from the classic Start/Stop/Continue method to the 4L approach (Liked, Learned, Lacked, Longed For) and the Sailboat metaphor. Each format comes with a time indication, facilitation instructions and example questions to spark conversation. The document also contains an action plan section where the team records improvement actions with an owner, deadline and measurable success criterion, ensuring that good intentions actually get executed rather than floating in the air. By evaluating the actions from the previous retrospective at the start of each new session you create a continuous improvement loop that helps the team collaborate more effectively, resolve blockers faster and raise the quality of delivered work across every sprint.
Variations
Start/Stop/Continue Retrospective
The most widely used format. The team sorts observations into three columns: things to start doing, things to stop doing and things that work well and should continue. Simple, accessible and suited for teams just beginning with retrospectives.
Best for: Best for teams holding their first retrospectives or for sprints where improvement areas are relatively clear and the team needs a quick, structured format without much facilitation overhead.
4L Retrospective (Liked, Learned, Lacked, Longed For)
A more reflective format covering four dimensions: what the team enjoyed (Liked), what they learned (Learned), what was missing (Lacked) and what they wish for going forward (Longed For). This delivers deeper insight than a simple good-versus-bad split.
Best for: Ideal for mature teams that have run multiple retrospectives and need more nuance than the standard good/bad categorisation, especially after sprints with significant learning moments.
Sailboat Retrospective
A visual metaphor where the team draws a sailboat with wind (what propels us forward), anchors (what holds us back), rocks (risks ahead) and islands (our goals). Encourages creative thinking and surfaces perspectives that text-only formats miss.
Best for: Perfect for teams that need variety or when energy is low and a visual, playful approach helps the team reflect openly and share fresh insights they might not voice in a traditional setup.
Timeline Retrospective
The team walks chronologically through the sprint and places positive and negative moments on a timeline. This makes it possible to spot patterns, such as recurring problems at the end of the sprint or energy peaks after certain ceremonies.
Best for: Suited for longer sprints or periods where a lot happened and the team needs a chronological overview to better understand the cause and effect of events throughout the iteration.
Lean Coffee Retrospective
A democratic format without a fixed agenda. Team members write topics, vote on the most important ones and discuss them in five-minute time blocks. After each block the team votes whether the topic deserves more time or to move on.
Best for: Essential when the team has widely divergent concerns and no single standard format covers them all, or when the team wants ownership over the agenda rather than a predetermined structure.
How to use
Step 1: Schedule the retrospective right after the sprint review, preferably the same day. Reserve 60 to 90 minutes for a two-week sprint. Send the team a brief invitation with the chosen format so everyone can prepare mentally. Step 2: Open the session with a quick check-in to gauge the mood. Use a simple scale of 1 to 5 or a word cloud where each team member describes in one word how the sprint felt. This lowers the barrier for open communication. Step 3: Present the chosen format and explain the ground rules. Emphasise that the retrospective is a safe space where honest feedback is welcome without personal blame. Step 4: Give the team five to ten minutes of silent time to individually write observations on sticky notes, either physical or digital via Miro, FigJam or Retrium. One observation per note. Step 5: Have each team member place their notes on the board and briefly explain them. Group similar items into clusters to make patterns visible. Step 6: Let the team vote on the three most important clusters via dot-voting. Focus the discussion on the items with the most votes so the available time is spent effectively on what matters most. Step 7: Discuss each selected cluster and dig into the underlying cause. Use the 5-Why method to move beyond symptoms and identify the root cause. Step 8: Formulate a concrete action per cluster with an owner, deadline and measurable outcome. A good action is specific and achievable within the next sprint, not vague or overly ambitious. Step 9: Review the action items from the previous retrospective. Were they executed? Did they achieve the desired effect? Celebrate improvements and discuss why any actions were not picked up. Step 10: Close the session with a brief checkout. Ask each team member to share in one sentence the most important takeaway from the session. Step 11: Document the results in your project management tool. Create a ticket for each action so progress is visible on the sprint board and actions do not get lost among other work items. Step 12: Rotate retrospective formats regularly to prevent retro-fatigue. Use this template as a menu and choose the format per sprint that best fits the team dynamics and the nature of the past iteration.
How MG Software can help
At MG Software we help teams establish an effective retrospective process that goes beyond surface-level feedback. Our agile coaches co-facilitate the first sessions with your team, introduce different formats and help formulate actions that actually lead to improvement. We analyse patterns across multiple sprints and flag structural bottlenecks that a single team sometimes overlooks. Additionally, we train scrum masters in advanced facilitation techniques such as liberating structures and systems thinking, so your team can run effective retrospectives independently. Whether you are a new team still learning how to reflect or an experienced team stuck in a format rut, we bring the energy and structure needed to turn continuous improvement from theory into daily practice.
Frequently asked questions
Related articles
Sprint Planning Template - Free Download & Example
Run focused sprints with velocity tracking and per-member capacity matrix. Sprint planning template with goals, story selection, and definition of done for scrum teams.
User Story Template - Free Download & Writing Guide
Write effective user stories with this template: role-action-value format, Given-When-Then acceptance criteria, story points and Definition of Ready checklist.
Kanban Board Template - Free Visual Workflow Management Guide
Set up your kanban board with this free template. Covers columns, WIP limits, swimlanes, policies and metrics for lead time and cycle time measurement.
Scrum Explained: Sprints, Roles, Ceremonies, and When the Framework Adds Value
Scrum structures software development into short sprints with daily stand-ups, reviews, and retrospectives. Discover how the most widely adopted agile framework works, which roles and artifacts it includes, and when Scrum is the right choice for your team.