Friday, May 31, 2002 11:26 PM
Nothing is forced in XProgramming, indeed because XP is agile, thus it's a list of good practice that you may or may not use.
But pair programming is the only "quantified" scope in XP, and it turns out to be not longer developping by pair or one on each computer.
So you should think about velocity in long or middle terms to be sure you do not want to be pairing. Pair increases quality, pair increases team adaptability, pair increases team comunication, ... And all this scopes actually will really increase middle and long term developpement.
But if you start with using XP as a coach and don't fill like pairing your team(s) then just don't for the moment and try other scopes until you feel safe. Then you coul'd try pairing and make your point of view, invente a pair method and then exchange your experience.