Again, goes back to the point of you can do anything poorly. Ours are 30-60 minutes and usually have good conversations about issues the team sees. More often than not meaningful change comes out of it.
The only meaningful change I ever saw come out of a "retro" was making daily standups async twice a week (done over Slack.) Then the manager didn't like that, so it was rolled back.
Most of the retros I'd just roll my eyes at. "What can we do differently?" cancel the retros...
Haha. Tell them we can't do anything differently because that would mess up the meticulous Jira/Agile flow we've setup in other meetings and have affirmed in retros.
It's a tactic for managers to feel better about themselves. Look, the team is expressing gratitude! I'm a success as a manager! If you want to thank someone message them on Slack. We don't need a 30 (or 60) minute meeting for an enforced feel good moment.
Uh hu, but since I gave a range obviously we don't have 60 minutes of issues every week. If I meant that, I would have said we have 60 minutes of issues every week instead of giving a range for the meeting length.
>It's a tactic for managers to feel better about themselves. Look, the team is expressing gratitude! I'm a success as a manager! If you want to thank someone message them on Slack. We don't need a 30 (or 60) minute meeting for an enforced feel good moment.
You're projecting so hard here.
(1) We didn't have a manager for a couple months now and retros went on unchanged.
(2) Talking about wins isn't an enforced feel good moment. It's about identifying things that worked well so that the team can continue doing them.
Your position is extreme and not everyone feels the same as you.
