|Industrial XP Pairing|
PairingTwo people work on the same task together, continuously reviewing
each other's work and providing feedback
The bulk of the design on XP projects occurs during pairing.
Two people work on the same task at the same time, continuously
reviewing each other's work. Whenever pairing is dropped from XP,
design quality takes a plunge, while the defect count rises
Two people can pair to write stories, storytests, code or
documents. It is common to pair across sub-teams pairing during
integration and smoke testing, or when implementing stories that touch
7 Risks of Solo Programming
Cross-PollinationIt is important to cross-pollinate across sub-teams from time to time, so the team has a working idea of the entire system, beyond individual specializations. It is also important to note that there are some pairing combinations may not make business sense - like pairing a mainframe resource with a java resource on a java/mainframe programming task. However, such pairings do make sense when timeboxed in the context of short tasks that involve talking to different subsystems.
Styles of Pair-Programming
Further ReadingPair Programming Illuminated by Laurie Williams and Robert Kessler.
PairProgramming on the Wiki Wiki Web. Pair Draw, a pairing simulation.
Pair Programming on ExtremeProgramming.org
eXPosures, Pair Programming