Agile Retrospectives Done Right - Agile Coach (2019)
What Are Retrospectives and How to Conduct Them?
Introduction to Retrospectives
- Retrospectives are a crucial Scrum ceremony aimed at reflecting on the previous sprint and identifying areas for improvement.
- They help teams evaluate what went well, what didn't, and create a plan for enhancing future sprints.
Structure of a Retrospective
- The retrospective occurs after the sprint review and before the next sprint planning meeting, typically lasting about 30 minutes per week of iteration.
- All team members should attend, with discussions facilitated by a designated person (Scrum Master, Product Owner, or any team member).
Five Steps to Conducting a Retrospective
Step 1: Preparation
- Gather necessary supplies: whiteboard/wall, sticky notes, pens, and timer. Clear space for activities.
Step 2: Setting the Stage
- Establish a positive environment by reminding participants of Norm Kerth's prime directive emphasizing understanding and continuous improvement.
- Encourage participants to leave distractions behind (phones/laptops) and clarify the time frame being discussed.
Step 3: What Went Well?
- Distribute sticky notes for team members to write down positive outcomes from the last sprint within three to five minutes.
- Focus on strengths rather than complaints; share ideas aloud while fostering empathy among team members.
Step 4: What Needs Improvement?
- Repeat the sticky note exercise but focus on areas that could be improved without assigning blame.
- Facilitate discussion around these points while avoiding immediate solutions or rebukes.
Step 5: Next Steps
- After discussing positives and negatives, identify concrete actions for improvement.