Hi, In the last week we have been trying a pair programming concept with our Polish Software Development Team. Let me present some feedback from this experiment. It was a two-day trial during which we had developer pairs working on code problems. The configuration was mostly: 2 people with one computer, but there were situations that pair-mates worked separately at their own desk. The most important thing we saw is that pair programming can increase efficiency of some problem investigation. Typically this would be problems which need a lot of digging, a very experienced developer or just a good debate to determine the solution. Of course pair programming as an idea is intended to be used while programming, but then it gives benefits to the quality more than to efficiency itself, I think. Another observation is that some investigation parts (like digging through many files or so) are more effective when using separate computers (work can then be split between developers). Getting opinions from the team, I've noticed that while some of them said that pair programming improved their efficiency, some other claimed otherwise - that the efficiency was lower (even if they worked on the same problem). It's quite obvious that this way of investigation/programming is good for some problem types and doesn't provide any benefits for some other. The problem can be keeping up. When you're sitting in front of a screen somebody else is scrolling up and down, switching files,and so on, it is hard to remain focus and you tire very quickly. That's why it's really important to change the way of work during pair programming. You need to be constantly aware of that you're not alone. Frequent active/passive developer switching is also important here and makes things slightly better. Generally this method requires some time from people to get used to it. I've seen some "mouse battles" when developers wanted to do two different things at a time but that will go with practice. Definitely investigation or programming in pairs lets you to learn a lot. Especially when an experienced developer is co-operating with inexperienced one. However there are people who don't like to be teachers and they can get tired quickly. Some other feedback was that this trial gave the developers more motivation. When you're working on problems on your own, you can easily get distracted by many unimportant things (mails, forum posts, rss news, UFOs landing outside the office window, etc.). When you lose your focus it's hard to find it again. When you work in pair, it's easier to 'keep the course' since you are constantly being watched and you have help that keeps you on track. To sum up: Compulsory pair programming for every problem would have no sense at all, but working in pairs on problems that are hard to investigate, replicate or fix is something worth trying. Cheers, Pawel
