> Forcing the team to pay attention is probably harder in an async conversation chain than a meeting but I don't think ineffective is correct.
I think this is a feature. If people aren't paying attention to asynchronous information, there's a problem. Either the information isn't useful or the team isn't functional.
It might fall under "non-functional team" but active listening/reading of usually banal but sometimes critical information is simply not an easy thing to do in a routine format. The information in a standup is team-wide because you do not know what will be important to who. It takes some amount of skill and discipline from the team.
Re:Daily standups should be async
by karatestomp on Friday May 15, 2020 @05:18PM
(#23197550)
Part of this is because the standard format encourages including shit that no-one cares about, or that a glance at the issue tracker or repo activity would (should...) clarify immediately if anyone wants to know. If your "no blockers" updates could be written by a very simple script maybe don't bother with those parts.
Or, god, worse if it's manager-centric and everyone's listing every little damn thing they did yesterday just to make sure they sound sufficiently busy. Ugh. No one gives a shit (except your manager, if they're bad and letting standups be used this way) do you need anything? No? Then move on.
We 1000% agree on this, but it's still fun to talk about.
I think that's just low signal to noise. It definitely takes skill and discipline, but it's also a matter of improving habits. Standups were originally a "better habit". There's a cost, though, especially as teams are more distributed (and diverse).
You want a way to voice your status, hear other's statuses, hear blockers, and reduce duplicated effort. You can do all this with short, daily, async updates. The synchronous fashion of the standup is mostly a factor of verbal communication, not a feature.
Standups are usually partially async as items that arise should be dealt with outside of the meeting.
It still needs to be daily and time gated such that the team can consistently read everyone's status.
Forcing the team to pay attention is probably harder in an async conversation chain than a meeting but I don't think ineffective is correct.