"Diversity in thought" is incredibly important to success in a project of non-trivial size, and if everyone thinks exactly the same way, it's all too easy to make bad decisions as a result of the echo chamber.
I imagine this is a major contributor to the failure of many startups -- we often laugh at the startups that come up with absurd business models that could obviously never work, or develop apps that clearly nobody would want to use, but simply pointing and laughing belies the truth: what happened was that they didn't have anyone who disagreed, who thought differently.
Sometimes you just need someone to point out that what you're doing is dumb, and that there's better options.
I suppose that someone on the team could have "known" that the product wouldn't succeed with customers before it shipped, but the strategy of knowing what will work with customers in advance is considered a bit outdated, especially in software which is now relatively cheap to prototype and get out in front of customers.
"Teamicide" is also a big reason for startup failures. (For an entertaining read with an overview of teamicide see: http://www.codinghorror.com/blog/2009/01/are-you-creating-mi...)
Yes, you're going to have some culture differences, but so what? Every company I've worked for has made it's own culture.
A _team_ from the same uni will be extremely productive if they focused on that type of project in their courses. If the team only has undergrad degrees, look at the undergrad projects, of course. But their strength will be in bootstrapping such a project, not maintaining it. (Work done for courses is perpetually being re-invented and never maintained, by its very nature.)
And the flip side of the coin is: break up that team and mix them up in your other teams, and they will learn a lot about the real world. As long as they're closeted together, they'll have that laser-focus and high productivity, but lack the real-world perspective.
If you only have one team of developers, you need the diversity! My small company really benefits from the variety of backgrounds we bring.
Then there are those 10x players who may have gone to the uni but worked outside the uni as well. They aren't vulnerable to this kind of thinking, but will work really well with other guys from their alma mater.
The notion that a great team has good communication seems pretty obvious. But drawing people from the exact same pool of talent is not necessarily a good thing to do at all -- in fact, it can be down right detrimental to the team. But to be clear, I am not saying that diversity is a cure either -- having too many opinions on how something should be done is also problematic.
I agree with the main premise of the article that you need a team of complimentary individuals. I think this touches on something that is similar to the notion of 'how to hire someone who is smarter than you are.' So hiring people that are like you, or the rest of the team, could be a mistake. Hiring people that compliment the current team is, IMHO, the right way to build a team.
I have experienced both sides of this coin: one team that on paper was probably not all that impressive, but came together and made a brilliant team. And the opposite, where the team was a collection of brilliant individuals from the same school who were unable to function effectively as a team because there was no leader and everyone thought their approach to a given problem was best.
So while communication is hugely important, I think that it is also essential to avoid hiring people who are like you or who you feel comfortable around simply because of a shared background.
(This is a company of 5k+ employees)
Of course, adding new member(s) to such a team should not require "PhD from UIUC". Rather, the team must also be able to absorb a member and teach him the vocabulary required to collaborate and contribute effectively.
Personally, I work as a technology/security expert in a team that consists of PhD, machine-learning experts. I've been taught enough vocabulary to understand and follow the conversation and be able to contribute and feel purposeful and innovative from my - very different - perspective.
(Sorry, couldn't resist.)
Having people who like hanging out with each other is very important for teams, especially small teams at startups.