A retrospective is typically run by a Scrum Master, Product Owner, or an agile coach. This facilitator ensures the meeting stays on time, maintains a productive, psychologically safe environment, and focuses on actionable improvements for the team.
The retrospective facilitator (often the Scrum Master or Product Owner) is responsible for running the meeting and keeping it on time. Everyone else participates, offering their views on what happened (good and bad) and how the team can improve for next time.
Knowing who is responsible for facilitating the sprint retrospective meeting is an important part of working in agile and Scrum. The Scrum master is responsible for facilitating these meetings. It's their job to ask everyone to contribute their ideas in the meeting - usually, in a start, stop, continue format.
It can be a team member from another team, be it that team's Scrum master or anybody else from that team who knows how to lead a good retrospective. Or it can be an agile coach, process responsible, quality manager, or even somebody from HR or a line manager.
Your sprint retrospective meeting should include the product owner, the Scrum team, the Scrum Master, stakeholders, and Rovo. During a sprint retrospective meeting, it's good to have a diverse array of perspectives in the room.
The retro is a place for the Scrum team to reflect on how they're working and look for ways to improve their work system. This means, the official Scrum Guide answer to, “Should managers join our team's retro?” is “No, it's just for the team.”
Typically retrospectives are run by the scrum Master or project lead, but you may want to consider bringing in a guest to facilitate your next retro.
The 6 steps needed for a successful retrospective are:
The Scrum Master plays a vital role in the successful delivery of all five stages. As its name suggests, the aim of the first step of the retrospective process is to set a tone and direction for the retrospective meeting.
The Core Retro Crew
The Developers who are doing the hands-on work. The Product Owner who defines and prioritizes the backlog. The Scrum Master who facilitates the Agile process.
What is the golden rule of retrospectives? To create a safe environment where team members can speak openly. It's essential to focus on continuous improvement rather than blame, ensuring that every voice is heard and valued.
The 3-5-3 rule in Agile (specifically Scrum) is a simple mnemonic for the core components of the framework: 3 Roles (Product Owner, Scrum Master, Development Team), 5 Events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective), and 3 Artifacts (Product Backlog, Sprint Backlog, Increment). It serves as a quick checklist for teams to ensure they are implementing Scrum correctly, promoting transparency, inspection, and adaptation for better value delivery.
Following are some common retrospective mistakes that can be made during a meeting and some tips you can use to effectively avoid them.
Most products follow the 80/20 rule, where a small portion (~20%) of features delivers most (~80%) of the impact. Identifying those high-value items and moving them to the top of the backlog ensures meaningful outcomes reach customers quickly.
In an agile environment, the PMO and Scrum Master can collaborate effectively to maximize the value and effectiveness of projects. An agile PMO can adopt and support agile principles across the organization, facilitating an environment where Scrum Masters and their teams can thrive.
One of the most common complaints about retrospectives is that people fail to bring up real issues or admit to their problems. If people aren't going, to be honest in a retrospective, the argument goes, they're a waste of time.
How to run a 4Ls Retrospective
The manager may indeed be a lovely human being. They may even be friends with many of the team members, but if they are the person in charge of determining promotions, writing performance reviews, etc, then generally, they should not be in the Retrospective.
The recommended way to run retrospectives is for the team to discuss how they can improve their way of working and pick one or two improvement areas for the next iteration.
3 Pillars of a Retrospective
Addressing Conflicts in Retrospective Meetings
Team lead is usually the facilitator for the retrospective, but this responsibility can also be circulated within the team. Product owner and other team members actively participate and share their ideas.
In conclusion, the Scrum Master plays a critical role during the Sprint Retrospective, as they are responsible for facilitating (maybe) and empowering the team to continuously improve (always). Before, during, and after the retrospective, the Scrum Master must help people open up and collaborate in a healthy way.
22 retrospective ideas for agile teams