We learned some fundamental rules for the pair programming
construct itself during the VCAPS project:
- Never pair two people together who are
brand new to programming in pairs (always one old-timer with a
- When a pair takes the option of working
separately (but with joint responsibility), they aren't really pair
- If both people can't see what is
happening on the monitor, they aren't really pair programming.
- Everyone works in a pair (no lone rangers
- People have to trust each other, and it
may take time to build trust among everyone on the team
I think most people who have done pair
programming unsuccessfully (and then successfully) have learned these
sorts of rules of thumb.