Agile development teams seem to appreciate the value of having standup meetings. They are easily adopted by teams.
Unfortunately, I can’t say the same thing about Agile Retrospectives.
One of the common problems that I’ve noticed is the lack of discipline with retrospectives, especially when it comes to defining and following up on action items.
It seems that retrospectives are being done to ceremoniously comply with the requisite of doing so rather than looking to establish a continuous improvement process. That’s when “retrospective fatigue” kicks in. That’s quickly followed by comments, like, “What is the point of doing this? Nothing is going to change anyways.” Is this your case? Here you'll learn how to make the most out of Agile Retrospectives. You can also read our post: "Overcoming reluctance towards Retrospectives."
You Might Be Too Busy to Improve
Based on what I’ve seen in the different projects I’ve participated in, and from other experts, some reasons are:
- Retrospectives are the only thing that holds back the excitement to begin planning new stuff. Everyone wants to get into a new iteration ASAP.
- There is no leadership.
- There are more complainers than doers.
- “Someone else must solve this.”
- No concrete action items are defined during the retrospective.
- Action items are hard to keep track of (and spreadsheets suck).
- Everybody is busy and action items are forgotten.
How to Implement Retrospectives
- Evangelize the retrospective process, make sure it is important to the team.
- Agile process simulation games help teams understand the value of retrospectives, especially the Ballpoint Game.
- Show the results of action items and share them with the team as soon as they are solved.
- Define owners and due dates for action items. Otherwise, no one will be responsible.
- Have action item owners share status during daily meetings as if they were User Stories.
- Start each retrospective by looking at the action items that came out of the last one.
What Can We Learn from Retrospectives?
- They are really simple to do.
- They help the team improve and get better results. Dev teams feel backed up and supported.
- Helps the team solve problems and improve themselves.
Trying to improve your #Agile practices? OR are you getting started with Agile? Are you in a remote team? Check out our products for Agile teams at SoftwareDevTools. We focus on making agile ceremonies more effective and easier to adopt for remote teams.
Check out our Atlassian tools:
- Agile Retrospectives for Confluence
- Agile Retrospectives for Jira
- Scrum Poker for Confluence
- Scrum Poker for Jira
- Stand.bot for Stride: A bot to automate daily updates.
- And for Slack also!