“Culture of Asynchronous Communication” was for many years a cornerstone of open source development. It’s notable how little analysis has gone into that. Most open source projects are coordinated with amazingly low bandwidth and extremely high latency. This is often one of the most difficult cultural conventions for people emigrating in from other software subcultures.
One neat, but certainly unintended, consequence of that was it created an audit trail that social scientists could pick apart.
We do not know if this is a necessary element to a high functioning open source project. Is there a sweet spot in the space of bandwidth and latency? What aspects of the task domain shift the location of that sweet spot?
I am confident there is a complement to Brook’s insight that “Assigning more programmers to a project running behind schedule, could actually make it even more late.”
Adding more bandwidth and lowering latency to collaborative work can make it less collaborative.