Maybe agile doesnt quite actually support our needs. Maybe some frequent socialising is a need. Maybe sucking every last second out of our day in the name of productivity while having zero benefit on the true goal is just one huge smell.
That thinking is an agile smell. Teams choose their own processes.
That's an interesting claim, but has it be proven or even seriously studied? I have an extremely hard time with open meetings talking without any depth about various subjects which I don't care about 90% of them; it might make me space out and at risk of missing the parts that I could actually be interested in or contribute. Plus this cultivate the importance of oral transmission, with informations easily lost and inaccessible for people unable to participate for various reasons. Maybe a good structured IM (e.g. dedicating a chatroom exclusively for that) could make it work better? I think it is important that the medium be the same for synchronous and asynchronous people.
Daily meetings can be extremely useful in context of routine transmission of info, mostly on always the same well-defined topics + a small amount of random very important things. The important infos must be hierarchized, you can not just drop them in the middle of a stream of boring "I continued to develop X yesterday and will continue to do it tomorrow". So on open engineering subjects, some people may like it and that may be effective for them, but I really want to know if this is the majority of people / for the majority of projects / ...
Focus on surfacing problems not solving them.
If you can successfully get unblocked async over slack/email/whatever, there isn't a need a for standups. That just means you have a functioning line of communication for your team.
Stand ups should solve the problem of "I need to get unblocked and I can't get my teams attention effectively". If async "standups" solve that, great. But it's not a one size fits all solution, and imo, shouldn't even be called a standup.
>But for the life of me, what I can't figure out is why some teams have good ones, and some don't.
IME it's the level of interaction of product/management/scrum-masters that make the difference. Good standups consist of just engineer focused updates/requests. Bad ones are progress reports and have participation of anyone not actively contributing to the sprint.