[antoinevg]

How about we just stop generalising across each others projects, teams and environments?

This stuff is always highly context dependent and the ongoing efforts of everyone to pretend it isn't makes it extremely difficult to have adult conversations on the topic.

[vfc1]

The use of unnecessary daily standups is an industry-wide practice that few teams escape, and it's important to talk about their general unusefulness and hidden costs.

It has been proposed originally as an agile "let's do what makes sense for each case" practice, and as quickly been adopted by companies as a common micromanagement practice.

Yes its context-dependent, but at the same time, its something so pervasive that most developers can relate to it and have or will experience it one way or the other.

[h0h0h0h0111]

For me, "agile" has always been about constantly trying new ways of doing things, keeping the ones that work and culling the ones that don't, fast. It's a process that changes as your team changes, as your goals change, and never works the same for two different teams. It amazes me that people can come along and unironically decry some process as outright bad or pointless

[mikorym]

> context dependent

Exactly. If you work for a financial company where a manager has to check every analysis, then of course you need such meetings. I don't think efficient people spend all their time reading about how to be efficient.

[debt]

“This stuff is always highly context dependent”

Well I think standups, on average across all possible developer contexts, are useless.

To put another way, standups are likely to be useless regardless of context.