From a Tedd Ziuba post hating on process . Software development methodology is organizational Valtrex. Sure, it treats a symptom, but the only cure for the underlying disease is to never have contracted it in the first place He goes on to point out that the main reason to have process/methodology is that, thanks to the Law of Large Numbers , the more developers you have, the more your average skill is going to regress to the mean, i.e., the skill of the Mythical Average Developer The underlying cause is that the variance of developer skill on your team is too high, which means your team can't execute well, and you need process to wrangle the laggards Communication Overhead In my experience, there is a second reason called, you guessed it, Communication Overhead . See, I am the Perfect Developer. Everything I do is Perfect. Crystalline Joyeous Glorious Perfection. (yeah, yeah. humor me). Oh, did I mention I don't need to sleep either? ...
