Discussion

Ask HN: Do retros that don't suck even exist?

If we do retros as they are, they can be a great way to bring meaningful changes to the team - but it usually doesn't.

Usually people start with a bi-weekly retro at the end of the sprint, debriefing everything including the incidents, then slowly it becomes a monthly thing, and surely enough whoever is loudest in those meetings gets to say whatever they want. It ends up being a waste of time and a huge disappointment. Also, no one really takes on the action items coming out of those meetings.

Why is it that a supposedly meaningful 60 min retro can suck so much?

Of course there's got to be some ways to ensure retros actually work. Or, is there?

6 points pypudding 2 years ago 18 comments

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton