The Windows Shutdown crapfest (2006)
&gt;  So in addition to the above problems with decision-making, each team had no idea what the other team was actually doing until it had been done for weeks.<p>The Open Source development model addresses this. By removing meetings and forcing all work to be done &quot;in the open&quot;, it is impossible <i>not</i> to know what is going on, because you can always just go look at what&#x27;s going on. Subscribe to the mailing list and you will always know what is going on. Or don&#x27;t and read the mailing list archives. Look at the patches, read the documentation, understand the context from discussions. There is no waiting for a team meeting, there is no arbitrary line of organizational hierarchy in your way. Just make a patch and send it in.<p>There are of course still delays and discussions and disagreements and whatnot; that&#x27;s the nature of collaboration with multiple humans with agency and ownership. But you never need 24 people to design a menu, because you just start <i>designing it</i>, and people can discuss the work asynchronously on the mailing list. There is no ceremony. All organization is ad-hoc, dynamic, decentralized, and just-in-time. By the time a large &quot;corporate&quot; team has finished building one feature, the open source developers have already released and tested three alpha versions.<p>I think every product owner should read The Cathedral And The Bazaar and put the bazaar method into practice (or at least try it!).