Agile Remote Retrospective 101
How to do a Remote Retrospective — Tools, Metrics, and Structure
What is a remote retrospective in Agile?
In Scrum, we have precise moments of planning, review progress, and learning, and improving. The retrospective enables the Scrum team to look behind on the sprint that passed and see what went well to continue doing it, what didn’t work, to stop it, and new things we should try. The retrospective is an intimate moment of honesty when we grow as a team. A remote retrospective represents an Agile retrospective where the participants are not face to face in the same meeting room, but connected remotely with the help of digital communication tools such as Zoom, Phone, Teams.
Who participates to the Agile Retrospective?
The retrospective is the event for the team, ONLY. No management, nobody outside the organization should participate. The main reason is because you want to discuss all those sensitive issues openly and the team to feel they aren’t judged. Face to face or remote retrospectives are an intimate time of the team. Keeping it only at the Scrum Team level is very important.
Who’s leading the Scrum Retrospective?
The Scrum Master facilitates the meeting call Scrum Retrospective.
My favorite digital tools for remote retrospectives are:
- IdeazBoard — has been my years-long favorite for its simplicity
- Confluence retrospective template — if you are using Atlassian
What to prepare for the remote retrospective:
- Decide on the theme of the retrospective.
2. Setup the digital board of the retrospective using an online tool. Prepare a sharable link that is easy to access for all the participants.
3. Gather data. The data helps the entire scrum team to learn about the things that went well, the sources of the deviations. The data supports the team to make informed decisions. The data must be accessible to everyone in a clear format. The team members must be able to visualize the metrics and to understand how they were gathered.
The most common retrospectives you can use while working remotely
- Lacked / Learned / Like
- Start / Stop / Continue
- What went well / What didn’t go so well / New ideas to try
- The weather retrospective: sun, clouds, storm
Ideas of less common remote retrospectives but that work very well for remote teams
- Draw your retrospective — ask the teams to draw how was the sprint from their perspective and present it to their colleagues
- The hero journey — appreciate the ones who help the team — it works very well after a tough sprint
- Root cause analysis
- The 5-whys
- Effort & pain / pleasure & gain
- Anchors and Engines
What data should you collect for the remote retrospective, and why?
- number of bugs
- user stories added during the sprint.
- user stories remove from the sprint
- user stories and story points moved to the next sprint
- user story completion rate
- user stories blocked
The reason why we gather all this information is that we want to analyze what could have impacted deviations from the plan so the team can take the needed corrective measures.
The agenda of a remote retrospective is
- Break the ice — remote teams need a warm-up, ice breaker to start to feel confident. The facilitator can use some jokes, so small talk to get everyone comfortable. I would recommend using video cameras.
- Set the Stage — welcome the participants. If you are remotely present, everyone who is part of the meeting for all the other participants to know. Introduce the list of the day and the tools the team will be using. Make sure everyone can access the tools you present, and they are clear for everyone.
- Gather Data — The scrum master shares with the team the data gathered and gathers more data from the scrum team if the case. The Scrum Master also helps with the interpretation of the data. It is essential to don’t spend more than 10 minutes on this.
- Generate Insights — Using one of the themes of your choice, allow everyone to insert their inputs into a digital tool. The active participation of all the team members is crucial for the success of the retrospective. Timebox the brainstorming to 5 minutes.
- Decide What to Do- ask everyone to vote a maximum of 3 topics they think it is essential to be discussed during the retrospective. After everyone voted, start from the items which received most of the votes. Discuss them with the team. Make sure the discussions are solution-oriented.
- Close the retrospective — wrap up the actions to be taken in the coming sprint and thank everyone for their efforts during the sprint.
What changes when you do a remote retrospective?
- try to keep it short because watching a screen for a longer period of time might be tiring and the participants might lose the focus
- You use a digital tool that is accessible for everyone
- everyone starts to contribute to the same board
- there are no chairs and tables that can avoid people more getting closer to the board and stick their post-its because everything is done in a digital tool
- there is no personal aspect about it, therefore is required for the scrum master at breaking the ice at the beginning
- You need to make sure that even the shyest speak
- there is the need for more precise communication
You might be interested in:
What are the nine questions you should ask yourself during the daily scrum that will keep you…
What I did yesterday to take the team closer to the sprint goal?
Agile Product Development as a small software development company?
How to get started developing a software product using Agile Methodology — my journey as a Product Owner and Agile…
Nine user story metrics I care about while coaching Scrum teams
Goal: put in numbers the team performance. Numbers talk to everyone. When we see 98% performance there is no…
Hamburger Method to Split User Stories from Dev team perspective
The main reason why I use the Hamburger Method to split user stories is to coach the teams to transit from the…
User Story Definition Of Done (DOD) in Agile Software Development and the Technical Debt
In Agile Software Development, we use the Definition Of Done for User Stories to ensure the quality of work and to…
15 Things you can do as Product Owner Improve Team Velocity
Dear Product Owners, I have good news for you: there is a lot you can do to help your scrum team to improve the…
15 Things you can do as Scrum Master to Improve the Scrum Team Velocity
Scrum team velocity is about consistency. When upgrading the Scrum team velocity, as an Agile Coach, I target:
29 Tips for Facilitators of Remote meetings
Send out an invitation with the topics to be discussed, the output of the meeting, full instructions on how to connect…
How to deal with Change of Requirements or Scope Creep in Agile?
Here are the questions I ask before accepting a change request? Does it serve the Sprint Goal? What is the business…
Remote Teams Misconceptions
Can you really manage remote teams effectively without face-to-face interaction?
Remote Feature Mapping Workshop
Feature Mapping is a technique that helps Product Owners, Product Managers, and teams to visualize the big picture of…