Phillipe on the AgileArticles group posted about a white paper from the Menlo Institute on Paired Programming. It is a great read and provides a pretty compelling argument for giving paired programming (usually the XP principle that gets the most resistance) a try at your organization. I especially liked that it discusses who to pair and answers many of the usual questions that debunkers ask. If you are trying to win over your management team, this paper may give you the ammunition you need! :-)
Be sure to download the PDF since it has one or two pictures which actually show the work environment. The first thing you will notice is the lack of cubes. I have only worked in cubes since arriving in the US in 2000 and I am not a fan ...
- False sense of privacy (everyone *can* hear your phone conversation anyway)
- Takes away casual interactions with artificial barriers
- Makes it difficult to have a sense of teamwork when everyone goes back to their separate cells
- One size fits all approach to corporate workers
Does anyone know where the concept of cubes came from? Was it some radical study done in the 60's? ;-)
I think a large open area of people doing the same type of work (essential to avoid noise) that can then be grouped together in teams and have more casual interactions is much better. One consultancy I worked at in the UK had 40+ developers in one big open room with long bench style desks - it worked great and was really quiet!