The article mentions Scrum, and its synchronous daily meetings. It fails to mention that Scrum is also largely supported by asynchronous communication, like cod

The article mentions Scrum, and its synchronous daily meetings. It fails to mention that Scrum is also largely supported by asynchronous communication, like code commits, review requests, reviews and documentation. The effect in my experience is that the purpose of the Scrum meeting is to offer a birds eye view of the asynchronous systems that make up the bulk of the development process, to enable participation and further comment. "The idea that a quarter of an hour of structured synchrony is enough time to enable a full day of work might sound preposterous" because it is. It's just there to kickstart the day and to give everyone a general idea of what's going on. For anyone doubting this, I suggest skipping a scrum meeting to see how much it actually impedes your work. Then, if you dare, try to avoid using the asynchronous communication that supports the development process for a day. Compare the results. Overall I just think that people should consider more carefully whether a topic is more suited for email, phone call or a meeting.