[celticmusic]

unrelated is relative. If I'm working on bug A and bob id working on bug B, I don't give a shit that bob is having to go talk to cathy in accounting about something.

They're unrelated tasks because there are no dependencies between them, and there is absolutely no reason why I should have to sit through bob talking about his day.

[bradstewart]

But the point of these, at least to me, is that someone on the team may know a way to get the problem solved without talking to Cathy in accounting. Sure, sometimes you listen to unrelated tasks, but many times (in my experience), somebody on the team can offer a bit of advice that helps everyone move faster.

EDIT: Spelling.

[celticmusic]

and now the "standup" has devolved to a design session, and I don't want to have to stand there while bob and betty have a discussion about it.

[kthejoker2]

The point of the standup is to figure out you need that design session, not to conduct it then and there.

Take ownership of the standup, don't just passively sit there and then complain afterwards what a waste of time it is.

[bradstewart]

It certainly can. We try to take those types of discussions offline though--Bob and Betty can have that talk after the standup.

And to clarify, I also find daily standups to be tedious and generally unhelpful. Once or twice a week seems to be the sweet spot (for me/my team).

[celticmusic]

right, Bob and Betty can have that discussion elsewhere. all of it. We don't need a standup for Bob and Betty to figure out they need to have that discussion.