A sprint retrospective is a collaborative team event where team members reflect on the previous sprint. They discuss what went well, identify areas for improvement, and brainstorm solutions. It’s a safe space for open and honest discussion, so attendance is limited to the core Agile team.
Here are some key points to remember about sprint retrospectives:
- Positive Language: Lean-Scrum emphasizes using positive language, even when discussing challenges or frustrations. The goal is to identify solutions, not assign blame.
- Actionable Outcomes: The most important outcome of a retrospective is a set of concrete actions the team will take to improve in the next sprint. Discussing past issues without a plan for improvement can feel unproductive.
- Reviewing Past Actions: During the retrospective, take time to review the previous sprint’s improvement actions. Did they achieve the desired outcome? Do any require further work?
Duration and Frequency
- Duration: 1 hour
- Frequency: at the end of every sprint
Objectives
- Discuss what worked well during the previous sprint and identify areas for improvement.
- Review progress on previously identified improvement actions and determine if they were achieved or require further work.
Who Attends
- Product Owner/Manager
- Delivery Manager/Agile Coach (facilitator)
- Business Analysts
- All Developers
- All User-Centred Design (UCD) team members (User Researchers and UX/UI Designers)
- Q/A
- Other technical roles (if applicable)
