Member-only story
Why Developers Hate Retrospectives
Originally published in GoRetro
How many times have you heard one of the following questions?
- Could we skip the retro this week?
- What about doing the retro every second or third Sprint?
- Could we postpone our retro?
- What’s the benefit of retros?
- I’ve got a lot to do. Would it be okay if I don’t attend the retro today?
I bet you’ve stumbled upon some of these questions if you’ve worked with Scrum teams. They often come from developers because they usually hate Sprint Retrospectives.
Developers search for excuses to skip retros when they see it as a waste of time.
Over the last few years, I identified four common patterns contributing to developers’ attitudes towards retrospectives, and I’d like to share them with you. Also, I will give you some hints on how to get developers interested in retrospectives.
#1 — Mechanical Retro
How does your Sprint retrospective run? Please, don’t tell me you always use the same dynamic. When I first learned about Scrum, I had a hybrid role, Product Owner and Scrum (which I don’t recommend, but it’s another story). I was inexperienced…
