[quartesixte]

As someone who works in a hard-tech startup, where daily standups in production manufacturing teams are part of the daily culture.

1) Anything longer than 15 minutes is insane 2) What do you even talk about for an hour? 3) Why do you even do standups for design work? What "blockers" could you possibly have that require daily, 15 minute tagups with the entire crew?

[marcosdumay]

On #2, nothing. People stay an hour trying to look busy because somebody on the meeting expect them to be busy and the meeting to be important. So they spend an hour talking about nothing.

On #3, blockers exist more on design than on operation. But the idea of a daily meeting to solve blockers is crazy-stupid. Imagine if operations did this, every time somebody's work get a wrong input, you'd stop their line until the next morning. That's why operations dailies aren't about blockers, and instead about information sharing. But design work doesn't have separate teams that need to share information, so they invent a bullshit reason to still have the meeting.

[kgeist]

>What do you even talk about for an hour?

We once had 1 hour long standups. The reasons were:

1) large team

2) many devs loved to go into detail about their work, and no one stopped them

3) the expectation was that a standup must be about describing what you did yesterday, in detail

What we did:

1) split the team into subteams where each team has their own standup (down to 5-15 min)

2) the standup's facilitator now stops devs from going into too much detail, "you guys can discuss it further after the standup"

3) now the expectation is that a standup should be about checking the project status and if there are any blockers, and that's it, you don't have to recount your whole yesterday in great detail

[RHSeeger]

> 2) the standup's facilitator now stops devs from going into too much detail, "you guys can discuss it further after the standup"

I said this in another comment, but a standup I'm part of tables these until the end of the call; and then anyone not involved in that conversation can drop off. It seems like a reasonable compromise to balance the need to get people together to discuss something against the need to not keep people tied up. It helps mitigate the issue of people not wanting to plan a meeting to just "talk about" something (when that's actually what is needed).

[RHSeeger]

One of the projects I'm on has a standup every day, and it generally lasts less than 15 minutes. Sometimes, a topic comes up that needs more discuss and it's tabled until the end of the call. At the end, anyone that doesn't need (or want, sometimes it's useful to just listen in) to be part of the additional discussion drops off and it turns from standup to technical discussion. It works pretty well.