If this actually rings true, there’s something pretty wrong in your team.
Stand up should be a quick and uncontroversial meeting talking about what you’ve done, what you’ll do and anything you need help with, plus maybe a couple of minutes of small talk before you start.
We waste the two hours doing code reviews that only three people actually need to be present for, I always appreciate the chance to zone out and do something else for a big part of the day. Follow that with lunch and I’ve just done half a day’s work by watching TV
My team does this for the first ~15 minutes and then we move to “group think” for any tough problems or “water cooler chat” for the remaining 15. You’re allowed to leave if it’s just water cooler chat, so I really like it
Problem is in practice, I suspect something is pretty wrong in most teams.
Some common examples come to my mind:
Management hears “talk about what you’ve done and what you will do” so great time to sit in and take notes for performance review, and it becomes a “make sure management knows you spent all your time and did really impressive stuff” meeting. Also throws a kink in “things I need help with” as there’s always the risk that management decides you aren’t self sufficient enough if they hear you got stuck, so you also need to defend why you got stuck and how it isn’t your fault.
The people who feel like everyone needs to know the minutia of their trials and tribulations including all the intermediate dead ends they went down on the way to their final result. Related to the above, but there are people who think to do this even without the need to impress management.
The people who cannot stand to “take it offline” and will stop everything to fully work a problem while everyone is still ostensibly supposed to stay in the meeting despite having nothing to do with the two people talking (sometimes even just one, a guy starts talking to himself as he tries to do something live).
Groups that are organized but have very little common ground. An “everything must be scrum” company sticks a guy who does stuff like shipping and receiving into a development team and there’s no ‘scrum-like’ interaction to be had and yet, there he is wasting his time and having to talk about stuff no one else on that meeting has a need to hear either.
If this actually rings true, there’s something pretty wrong in your team.
Stand up should be a quick and uncontroversial meeting talking about what you’ve done, what you’ll do and anything you need help with, plus maybe a couple of minutes of small talk before you start.
You mean you’re not actually supposed to spend 2 hours daily unfucking everyone’s shit during the standup turn by turn?
We waste the two hours doing code reviews that only three people actually need to be present for, I always appreciate the chance to zone out and do something else for a big part of the day. Follow that with lunch and I’ve just done half a day’s work by watching TV
My team does this for the first ~15 minutes and then we move to “group think” for any tough problems or “water cooler chat” for the remaining 15. You’re allowed to leave if it’s just water cooler chat, so I really like it
That sounds about 25 mins longer than i’m willing to call a standup.
if it’s not wrapped up within 10 mins of the scheduled start time something has gone horribly wrong
Yeah but I’m retarded and don’t want my team to know I’ve been struggling to make a proper AWS SQS topic policy for the past three days
Real. Or in my case I’m depressed and fucked up and just haven’t found the motivation to even open my IDE…
Problem is in practice, I suspect something is pretty wrong in most teams.
Some common examples come to my mind: