Obviously we’re big fans of retrospectives at Metro Retro and it may seem like a clickbait title, but I promise I’m being serious here.
Most people hold their retrospectives at fixed intervals or after significant events like the end of a Scrum team’s sprint, the release of a software update, or after a marketing campaign. The retrospective is used to improve the team going forward by looking back on the ways the team has worked together. At most this retrospective is held weekly, but often they will be held every two weeks, monthly or longer.
When we ask Agile coaches what the first thing they do with a new team is, the majority say:
"Retrospective, retrospective, retrospective!"
At the risk of sounding like a crazy person, there's a reason for it - they believe the retrospective is one of the most valuable exercises for a team to do together.
My point here is to ask: is it better to wait long periods of time for your next valuable retrospective and try to tackle one or two big improvements that come out of it, or could it be beneficial to make smaller improvements at quicker intervals?
Running a small, daily retrospective is one way to focus on constant improvement, and I encourage you to try it as an experiment.
Lastly, you do not have to use a tool like Metro Retro to run this retrospective, it can be as lightweight as just having a group conversation. However if you did want to use a template, I suggest something simple like the Worked Well / Kinda Worked / Didn't Work retrospective template.
Sign Up for free to create your own daily retrospective board!