Sprint Retrospectives: A Complete Guide for Agile Teams
Sujith G
Table of Contents
Introduction
One of the main principles of agile ways of working is to inspect and adapt. The iterative and incremental development brings in the benefit of continuously improving the product along with people and process. While at the end of every iteration, product increments with features, there is also another ceremony which is recommended to ensure there is improvement with respect to people and process. Sprint retrospective is one forum where the teams get together to reflect on how their experience was in the previous sprint and how they can make it better in the upcoming sprint.
In our experience as an agile consulting company, we have seen many teams misuse or not make full use of retrospective meetings and the main reason is the inability to understand the intent behind the ceremony and making it just as a checklist meeting. This could cause a lot of fatigue in the team and eventually reach a point where retro becomes just a meeting. So, in this blog we aim at exploring and understanding:
What is a Sprint retrospective?
The purpose and intent behind the Sprint Retrospective event.
How to drive a sprint retrospective meeting?
How can sprint retrospective help agile teams?
So Let’s Start!!!
What is a sprint retrospective?
A sprint retrospective is a recurring meeting held on the last day of the sprint to reflect on the past sprint and identify what could be improved. It is one of the four ceremonies which are recommended by the scrum guide. While there are thousands of templates to facilitate a retrospective meeting, the intent however remains the same and that is to understand the positives in the past sprint, areas of improvement and get consensus regarding the action items to improve. A sprint retrospective is:
Held on the last day after the sprint review
Timeboxed for 1 hour for a 2 week sprint
Scrum master facilitates it and development teams participate in it
Output is actionable items which will help teams improve in terms of process and people
Where retrospectives fit within the Agile and Scrum framework?
The main fitment of sprint retrospective is around the cycles of inspection and adaptation along with continuous improvement which is one of the core principles of agile. Agile Retrospective meetings are held at the end of every sprint giving teams an opportunity to reflect on their previous sprint and improve.
In Scrum, retrospective is one of the 5 ceremonies that takes place right at the end of the current sprint and before the next sprint planning starts. The outcome is a plan for implementing improvements in the next sprint
From an Agile perspective, Retrospectives supports the principle – “At regular intervals, the team reflects on how to become more effective and then tunes and adjusts accordingly”
What are the core principles of effective retrospectives?
To make full use of sprint retrospective is by ensuring a safe, structured and solution focussed discussion that helps the team improve. Below are a few key principles to make a sprint retrospective even more effective:
Keep it Timeboxed – Every sprint ensures the retro happens for not more than 45-60 for a 2 week sprint. Keep it structured and concise
Showcase Improvements – Talk about retro points from previous sprints and check on the improvements
Safe and Open environment – Create an open blame free environment where team members feel comfortable to share their suggestions
Use Data to discuss – Use readily available data to discuss any debatable points to ensure every one is aligned
Outcome Driven – Every retrospective ensure there are 2-3 action items which will help teams improve
Who Should Attend a Sprint Retrospective Meeting?
The sprint retrospective is for the entire scrum team. Development team who are directly the doers of creating the increment. Product owner as their insights on the increment delivered are valuable and the scrum master who actually facilitates the ceremony.
While the stakeholders and managers who are not part of the scrum team are optional unless invited by the team to address a particular impediment or provide specific support.
The role of the Scrum Master as facilitator in Sprint Retrospective
Scrum master plays a vital role in making the retrospective effective. Below are a few key points a scrum master needs to ensure as a facilitator:
Pre meeting:
Send the invites well in advance
Choose the right type of retro to conduct
Prepare retro boards for the team
During the Meeting:
Set the agenda and the norms to the participants
Ensure a safe environment for the participants to share their views
Skip to content 
