Even 10 minute meeting is disruptive. Usually they are in the morning when most people are at their most productive and it takes you out of the flow. Even a 5-10 minute meeting will destroy 30 minutes of productivity from context switching.
Ultimately it's about maximizing the productivity of the team or engineering organization at large more than it is about optimizing the productivity of a single developer. This often means that it's worth creating a mild disruption for individuals if it prevents the team from falling into a dis-coordinated state that can take days or weeks to recover from.
I get it and to a large extent, I agree, but it's not a random phone call or interruption, it's a scheduled meeting, which is easy enough to work around.
Interruptions are frustrating (don't get me started on phone calls), but when you are working on a project collaboratively, touching bases and knowing what other people on your team is doing is important.
I'm not against collaboration or communication. On the contrary I think it's critical to well functioning and productive teams.
I just think stand ups as I've experienced over 10 teams and 5 organizations haven't been especially useful. They have been a status update mostly for the pm and a little for the tech lead.
What is an example of helpful information you guys are sharing in your stand ups?
At my current job, It's where pretty much all information about our project gets disseminated so without it, we'd be feeling around blind. Any priority changes; changes which might not be well defined in the wires or stories; deadlines; information about meetings with the clients. It's also the place where the dev team, design, and QA touch base so if an issue comes up where there are pieces missing in the wires or QA is struggling to test something, we can quickly bring it up.
A big chunk is actually most useful for the PM, but often enough other issues get addressed that our short status meetings don't bother me.
Asynchronous communication--Slack, Discord, Teams, etc.--beats this every time. Why wait an entire day to bring up important topics? And then, if you aren't waiting an entire day, why have the artificial morning ceremony?
I love chat rooms, but they are their own kind of interruption and you can often communicate more in 2 minutes of conversation than in 45 minutes of back and forth on slack. And again, there are benefits to knowing when important things are going to be discussed and planning around that rather than have them happen at random in Slack.
