It's supposed to be a reality check to see how well estimates are matching up to actual effort. Which I don't really see why you shouldn't do something like that.
It's supposed to be a reality check to see how well estimates are matching up to actual effort. Which I don't really see why you shouldn't do something like that.
Most of the retros I'd just roll my eyes at. "What can we do differently?" cancel the retros...
> We talk about wins and things that go well too.
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.
The team doesn’t constantly need to reinforce what is working. That is self-evident and could be an email or slack message.
I’m done with this thread.
Taking your experience and making definitive statements is the definition of projection.
>The team doesn’t constantly need to reinforce what is working. That is self-evident and could be an email or slack message.
So you say. Obviously other people disagree