[aalleavitch]

There's a lot of roles on a team, though, and some of them require "soft skills" more than technical skills. For instance, your scrum master is probably better served by having strong people and management skills and a more general understanding of the technical problems the team is facing on a day-to-day basis rather than a deep understanding of implementation details. The idea wouldn't be to focus on staffing a team full of "soft skills" people, but rather to fill your team with people who cover a broad range of different skill sets applicable to different situations. So maybe you've got a hard computer scientist who can pound out complex implementations in a few seconds; she's probably ultimately going to really appreciate having a teammate who's better at condensing the scatterbrain designer's ideas into a hard set of specs that won't require as many back-and-forth feedback iterations even if said teammate isn't as good of a programmer as she is.