review · Retrospective, Feedback, Problem Solving · 45–180 min · 4-8 people · medium energy

Sprint Retrospective

A Sprint Retrospective is a recurring meeting held after each sprint to reflect on what went well, what could be improved, and to create actionable steps for future sprints. This process fosters continuous improvement and enhances team reflexivity, leading to better decision-making and problem-solving.

When to use Sprint Retrospective

Use this method at the end of each sprint (or every other sprint for very short sprints) to identify areas for improvement in team processes, communication, and overall performance.

What it solves

Lack of continuous improvement, recurring issues in sprints, poor team communication, resistance to change.

How to run Sprint Retrospective, step by step

  1. Set the Tone (5 min) - Emphasize psychological safety and a blameless culture. Encourage open and honest feedback focused on improvement.
  2. Gather Feedback (15 min) - Use methods like open discussion, surveys, 4Ls (Loved, Loathed, Learned, Longed For), or Sad, Mad, Glad to collect diverse perspectives.
  3. Turn Feedback into Insights (20 min) - Identify patterns and trends in the feedback. Discuss what changes could be made to build on successes and minimize failures.
  4. Create Action Items (15 min) - Convert insights into specific, measurable, achievable, relevant, and time-bound (SMART) action items. Assign owners and deadlines.
  5. Conclusion (5 min) - Thank participants, summarize key takeaways, and reiterate action items. Ensure everyone understands their responsibilities.

Materials needed

  • Meeting space or video conferencing with screen sharing
  • Digital collaboration tool (e.g., Miro, Mural, Confluence)
  • Timer
  • Optional: physical whiteboard, markers, sticky notes

Facilitator tips

  • Encourage participation from all team members, especially quieter voices.
  • Focus on patterns and trends rather than individual incidents.
  • Ensure action items are specific and actionable, not vague or aspirational.

Common pitfalls

  • Lack of feedback due to fear of blame. Create a safe space and encourage anonymous submissions.
  • Focusing on one-time mistakes. Steer the conversation towards systemic issues.
  • Action items that are not implemented. Follow up on progress in subsequent retrospectives.

Variations

  • Use different retrospective formats (e.g., Starfish, Sailboat, Speedboat) to keep the process fresh.
  • Incorporate data from sprint metrics (e.g., velocity, burndown charts) to inform the discussion.

Running it online or hybrid

Use a digital whiteboard tool like Miro or Mural to facilitate remote collaboration and capture feedback.

What it produces

A list of actionable items with assigned owners and deadlines for implementation in the next sprint.

Origin

Adapted from Atlassian Team Playbook — source

Build a session around Sprint Retrospective

METODIC places Sprint Retrospective inside a complete, timed session plan — agenda, worksheets, facilitator guide and slides — matched to your group and goal.

Generate a session with Sprint Retrospective · Try METODIC free