Almost everything in the modern world is fast-paced: fast food, fast fashion, and a neverending stream of Fast & Furious movies. It only makes sense that you have a fast option when it comes to conducting a retrospective on your sprints. They are called sprints after all.
Maybe your team is just experimenting with starting retrospectives. Or you truly don’t have time in all your tight deadlines to all sit down together for half an hour. Either way, we’ve got the perfect retrospective for you: the aptly named quick retrospective.
Find our convenient quick retrospective template in Cacoo to get started with your own run-through.
How to keep it quick
The Quick Retrospective may not look too different from other retrospectives like Mad Sad Glad, Keep Problem Try, Start Stop Continue, and especially the 4Ls Retrospective. But, we can assure you, with this one, it’s all in the timing.
While other retrospectives may range between five to fifteen minutes per suggestion (or unlimited time if you have it to spare and hit a good talking point), it is essential that each point made during this meeting is less than a minute long.
Send out directions (or this blog) so team members know what to expect and your retro template. They should come to the retrospective meeting with exactly one idea to place in each category.
The meeting can either be held in-person in a boardroom. Make sure you have a whiteboard or a screen to share your Cacoo template or online, where all members can log in and edit together in real-time. Allowing team members to fill out and add their stickies to the template ahead of time can save you even more time as a full team if you’re really in a crunch.
What was good?
When everyone is gathered, they should already know the drill and have their four ideas ready. Start with the ‘What was good?’ category. Go around to every team member and allow them to share one thing that went off without a hitch in your most recent sprint. Each person can talk for one minute maximum. Make sure to be strict in holding to this rule.
Once everyone has shared, you will see a list of things not to be touched in your next iteration. Maybe you even see a pattern of people listing this same thing. This only reinforces that that particular aspect went well and hopefully doesn’t signify that only one aspect of the project went well.
What was bad?
Just like the last step, everyone gets up to one minute to share one thing that they think went badly in your last sprint. If they had a list of things, this is where prioritization comes into play. Everyone must choose the ONE thing that they think needs to be improved. If that improvement is made in the upcoming iteration, they can always suggest another idea for the following sprint.
When everyone has had their chance to add to the list of bad aspects of the project, you can move on to working to solve these issues.
Take a look at the list of issues from the previous step. If you have a larger team and need to slim down the list, you can conduct a quick vote here where every team member gets to choose their top three issues. After voting has ended, you can eliminate the lesser voted on issues to deal with a shorter list (feel free to leave the list as long or short as you think you can hand for the next sprint).
Next, either leaving team members to think by themselves or put them in pairs or small teams, give them five to ten minutes to brainstorm ideas that could help to solve these issues. That can include getting to the bottom of what may be causing the issue, or coming up with some actionable items that could serve to improve the process next time around.
When time is up, have them share their ideas and add them to the list under the ‘Ideas’ category. Again, depending on how long or short this list ends up being, you can conduct another vote. Then you can choose which ideas seem like they are worth testing before moving on.
The final step builds on the previous step again. Looking at the ideas that the team put forth, create a plan of direct action. That way the team or an individual performing in the next iteration can solve the problem in the ‘Bad’ category.
Make sure that the action has a specific assignee. That way it doesn’t get forgotten when the work starts and tight deadlines start coming at you.
Take notes on the meeting and send them out after the meeting is over. Then you can track how each new action is working to solve the proposed problems. These will be worth touching upon at the beginning of your next retrospective.
Aaaaaaaaaand… that’s it! Just as quickly as promised!
The Quick Retrospective is straightforward and easy to conduct. But, as you get further into a project and more used to conducting retrospectives, it’ll be worth finding a more in-depth method that works well for you. This could be any of the ones mentioned above or ever the Starfish Retrospective.
Fortunately, Cacoo offers a variety of retrospective templates to experiment with and find which one is the best fit for your team. You can also find a quick guide to six types of retrospectives to learn more and help decide which option will be right for your team.
Once you’ve gotten started taking this look back at your sprints, you’ll find ways to constantly improve and speed up. There’ll be no need to look back!