A retrospective is an Agile/Scrum team meeting held at the end of an iteration (sprint) to reflect on past work, identify successes and failures, and create a plan for improvements. It facilitates honest, blameless discussions to optimize team performance, typically focusing on what to keep, start, or stop doing.
A retrospective meeting should bring together all teams and team members involved in both of these loops. At this meeting, at least one representative from each group should be given time to share their view of the overall development experience. The more people that you can fit in to speak with, the better.
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 retrospective format
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
Following are some common retrospective mistakes that can be made during a meeting and some tips you can use to effectively avoid them.
Sprint retrospectives can be as short as 45 minutes or as long as 3 hours — it all depends on the sprint. While you want to be efficient in everything you do, it's important to give your team enough time to have a meaningful discussion and make progress during a sprint retrospective.
Retrospectives should be easy in theory. Just ask a few questions – What went well? What didn't go well? What did we learn?
Before the retrospective meeting even begins, clearly explain why you are having a retrospective meeting. Discuss what its purpose is, and why it must be conducted so soon after the sprint is finished.
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.
Sprint Retrospective "Stop" Examples
Stop continuing to use an outdated tool that has proven to be inefficient. Stop spending too much time on non-priority tasks that do not directly contribute to project goals. Stop ignoring feedback from team members and stakeholders. Stop adding too many stories into the sprint.
Embrace the five stages of a successful Retrospective
Generate Insights: Unpack the data and analyse or look for the root causes. Decide what to do: Make sure the team decides what's most important together. Close: Appreciate people's time and get feedback on how to improve your retros in future.
The 5 Cs of Scrum refer to the core values that guide behavior and decision-making in the Scrum framework: Commitment, Courage, Focus, Openness, and Respect, which empower the pillars of Transparency, Inspection, and Adaptation, fostering trust and successful product development. These values help teams navigate complex projects, encouraging individuals to commit to goals, have the courage to tackle tough problems, focus on sprint work, be open about challenges, and respect each other as capable individuals.
According to this definition of the Scrum Team, the manager should not participate in Sprint retrospectives. Consequently, we can draw a first answer exclusively based on the Scrum Guide - and therefore 100% theoretical. The manager has no place in Sprint retrospectives.
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.
The 6 steps needed for a successful retrospective are:
The goal of a retrospective is to look back on a project, assess outcomes, and identify areas for improvement.
Sprint retrospectives should only be attended by the people who executed on work in the sprint. That includes: The sprint leader: Scrum Master, or Product Owner. People who executed on the work: Engineers, Developers, and Designers.
Summing up: Don't wait until people are getting bored in retrospectives. Change your retrospective facilitator, setting, and exercises frequently, invite people, reflect on how you are doing your retrospectives and celebrate successes so that your teams stay fresh and keep coming up with useful improvement actions.
An icebreaker is a great way to get your team talking in a fun, easy, and engaging way. It helps everyone feel comfortable and sets a positive tone for your retrospective. This is an optional step. You can set up different types of icebreakers: A random icebreaker based on a category.
Retrospective means looking back. An art exhibit that cover an artist's entire career is called a retrospective because it looks back at the work the artist has produced over many years. Retro- means back, -spect- means look (think: spectacles), so the word means literally 'a looking back.