We do Scrum but… we don’t do retros because everything is awesome!
Are you serious? — Episode 57
You had an awesome Sprint! The Sprint Goal was reached, stakeholders are ecstatic that your CI/CD pipeline is emptied and are hungry for more. Everyone in the team has a smile on their face. And then someone says what everyone is thinking:
“Cool, perfect sprint, we don’t need a retro!”
It’s like you’re dreaming, right?
Well, I advise you to wake up!
Do you really believe that nothing can be improved? Here’s a wicked question: How do you know? You’re not having retros. So how do you know that you have nothing to improve?
But OK. Let’s assume that you’re indeed working in the perfect environment. Will there never be changes that require you to adapt? I can’t believe that you believe that, because:
In complex environments things don’t stay the same.
- Changes in the market. Your competition advances too and the world is changing faster and faster.
- Changes in the organisation. I have never seen an organisation that doesn’t change. These changes impact teams and individuals. And it can’t be all good.
- Changes in team dynamics. People can join the team, others can leave the team. People change. Relations change.
- Evolving technologies. If you wish to be on top of the game then you have to adapt.
I could go on, but I think you see where I am getting at.
I don’t believe in fairy tales. “Skipping the Sprint Retrospective because everything is perfect” fits in my book of fairy tales. I think it’s an excuse to avoid discussing uncomfortable truths. A very unconvincing one.
Here is my advice: start doing Sprint Retrospectives again. If you do it well you will be surprised about the improvements opportunities spawning from it.
I hope you learned from this wake up call.
For more on Sprint Retrospectives, see this amazing article:
My twitter profile is https://twitter.com/WJAgeling
Do you want to share an article in Serious Scrum? Connect with us and make it happen!
We also have a LinkedIn group to share our articles and discuss Scrum.