Sprint Retrospective is the last event in a Sprint that helps Scrum team to inspect people, processes, tools, techniques, practices and Definition of Done and identify actionable improvements to become better. Making a Sprint Retrospective effective involves fostering an open and constructive environment where the Scrum Team can reflect on their recent Sprint and identify ways to improve.
1. Gather the Data
- The Scrum Master should get the data about the current Sprint preferably in a graphical representation (infographic).
- The data includes:
- What was the Sprint Goal?
- How many Product Backlog Items were planned to achieve the Sprint Goal?
- How many of the planned items were done?
- What was the available capacity?
- What was the utilized capacity?
- What impediments occurred during the Sprint?
- Open date and close date of the Impediments?
- Average cycle time taken to resolve impediments?
- Any unplanned items added to the Sprint Backlog?
2. Set Clear Objectives
- Define the purpose of the retrospective: inspect the Sprint, identify successes, and plan improvements.
- Make it clear that the meeting is to identify “What” is the problem but not “Who” so that the members do not focus on personal attacking or blaming
- Introduce the tool/technique that will be used to facilitate the retrospective so that the members will be familiar
3. Create a Safe and Trusting Environment
- Ensure that team members feel comfortable sharing their thoughts without fear of judgment.
- Promote a blameless culture focused on processes and systems rather than individuals.
4. Use Facilitation Techniques
- Rotate facilitators (if not always the Scrum Master) to bring fresh perspectives.
- Employ techniques like 4L (Liked, Learned, Lagged, Long-for), Start/Stop/Continue, the Sailboat exercise, or “Mad/Sad/Glad” to spark discussions.
5. Timebox and Stay Focused
- Keep the retrospective within the recommended timebox (up to 3 hours for a 4-week Sprint, shorter for shorter Sprints).
- Stick to the agenda to ensure productive use of time.
6. Encourage Engagement
- Use interactive tools or techniques like sticky notes, voting, or online collaboration platforms for distributed teams.
- Encourage quieter team members to contribute with direct but respectful invitations to share their thoughts.
7. Focus on Actionable Outcomes
- Identify specific, actionable improvements rather than vague ideas.
- Limit the number of changes to what is realistically achievable in the next Sprint.
8. Review Past Actions
- Start by reviewing the implementation and results of previous Sprint Retrospective action items to ensure continuity and accountability.
9. Celebrate Successes
- Recognize achievements to boost team morale and reinforce positive behaviors.
10. Adapt and Experiment
- Regularly experiment with different retrospective formats and tools to keep the process engaging and fresh.
11. Document and Share Outcomes
- Record insights and action items in a visible and accessible way for reference and accountability.
- Keep documentation brief and focused.
By continuously improving the retrospective process itself, the Scrum Team can maximize its effectiveness in fostering continuous improvement and team cohesion.
In order to understand some practical techniques to conduct the Retrospective, attend our CSM online training in Hyderabad. Learnovative’s Advanced CSM training also helps you to get familiar with advanced facilitation techniques.