Our beloved Scrum event, from the Latin word retrospectare that means "look back". This event has a specific meaning in our world of software development, both positive and negative. The retrospective is a chance for the team to inspect itself and create a plan for improvements in the next sprint.
Do not create a skipping habit
I have been in cross-functional teams that as time passed started to operate really well. The communication improved, the team found its pace, and conflict was handled constructively. But it all came to a point where members of the team said things like: "Should we skip the retrospective? We don't have anything to talk about."
In my experience, these are warning signs. A team that believes it has nothing to improve is either in denial or has stopped paying attention. The retrospective is not just a problem-solving session — it is a ritual that keeps the team honest and connected.
7 tips for your upcoming retrospectives
If you have a deadline or a release coming up, use the retrospective as a futurespective to focus on the upcoming challenges rather than past ones. This helps the team prepare mentally and tactically for what's ahead.
Instead of having the team wait for the retro to suggest topics to talk about, set up a "Retro inbox" on the wall or in a shared document. Team members can add items throughout the sprint, so nothing gets forgotten and the retro starts with real material.
If there is some extra time in a retro, be creative and uncontroversial. Once I made a team pick notes from a hat where everyone had written something they appreciated about a colleague. Small gestures like this build psychological safety.
A lot of teams follow the Scrum Guide and have the retrospective every sprint as they should, but they feel like they don't get any results from it. The reason is almost always the same: no concrete action points with owners and deadlines. A retro without follow-through is just a conversation.
This might sound silly, but usually the retro is held in a small conference room with no particular atmosphere. You can change the feeling of the retro and make it more special by providing snacks and drinks. It shifts the energy and signals that this time together matters.
I have been in retros where topics are all about code, servers, and infrastructure. Never forget to be human and talk about feelings and relationships. How are people doing? Is anyone burnt out? These questions matter as much as any technical concern.
Nobody likes to be forced into anything, especially not when it might put them in a socially awkward situation. Making attendance optional — while still making the retro worth attending — is a strong signal of psychological safety. The team shows up because they want to, not because they have to.