Sprint Retrospective

Sprint Retrospective format

What went well?

Discuss the positive aspects and successes from the last sprint.

Encourage the team to share specific examples and appreciate each other's contributions. This builds morale and reinforces good practices.

What could be improved?

Identify areas of improvement, challenges faced, and potential roadblocks.

Create a safe space for open and honest feedback. Remind the team that the goal is to learn, not to blame individuals.

What actions can we take?

Propose specific steps to address the areas for improvement.

Encourage the team to suggest concrete and actionable steps. Assign owners and target dates for key action items.

What still puzzles us?

Surface any open questions, concerns or areas needing further discussion.

This topic allows the team to park outstanding issues for later exploration. Assign owners to investigate and report back.

When to use this retrospective

• At the end of each sprint or iteration to review the team's performance and identify areas for improvement.
• When a team is facing recurring challenges or roadblocks and needs to adjust their approach.
• After a major project milestone or release to reflect on lessons learned and plan for the next phase.
• When a new team is formed or when there are significant changes in team composition or dynamics.

Suggested icebreaker questions

• If our team was a vehicle, what kind would it be and why?
• What's the most valuable lesson you've learned from a past project or experience?

Ideas and tips for your retrospective meeting

• Create a safe and judgment-free environment for open and honest discussion.
• Encourage participation from all team members and value diverse perspectives.
• Focus on identifying actionable steps rather than just listing problems.
• Assign owners and target dates for key action items to ensure follow-through.
• Celebrate successes and recognize team members' contributions.
• Keep the retrospective time-boxed and focused to maintain engagement.