« Test Driven Development in Java: Live and Uncensored | Main | Naked Planning and Other Risque Topics on the Improving Podcast »



TrackBack URL for this entry:

Listed below are links to weblogs that reference People Are Not Your Most Important Asset:


Feed You can follow this conversation by subscribing to the comment feed for this post.

Dan Quinn

Relationships and barrier removal are vital to successful projects, but the people need to be good for those two assets to be successful. Bad and/or unmotivated coders won't produce good code just because you put less processes and documentation requirements in their way. Good relationships won't get build if people naturally don't get along or like to work with others.

Ben Rady

Given the choice between a cohesive team of junior developers, and a team of experts who won't talk to each other, I'll go with the team of juniors. Changing interpersonal behavior is really hard. Teaching technical skills is easy by comparison.

Andrew Kazyrevich

Well, I doubt if you really think that a team of juniors is better than a team of experts - unless you also plan to save some money on juniors ;)

But I'm totally agree with relationships being the most important asset. It's esspecially evident on distributed teams - personal bonds get created quite slow there, while having good communication between local sub-teams is as good as gold.

Great post. In Microsoft's "Distributed agile development" paper they mention this idea several times as well: invest in relationships and don't break up good teams.

The comments to this entry are closed.