Pair programmign
3 posts in topic
Flat View  Flat View

Posted By:   Anonymous
Posted On:   Thursday, May 30, 2002 05:46 PM

Is pair programming a must thing in XP? This should be done whenever the task is complex. But if the task is very easy, and 2 developers can work quickly on different machines, why to do the pair programming in that case?


Re: Pair programmign

Posted By:   Dave_Astels  
Posted On:   Wednesday, June 12, 2002 02:21 AM

It is true that part of an agile process is adapatability.. being able to adapt the process to work the best for you. BUT To quote Beck in "XP Explained" Chapter 23 "20-80 Rule":

"The full effect of XP will not come until all the practices are in place. Many of the practices can be adopted piecemeal, but their effects will be multiplied when they are in place together."

So, yes, you can drop pair programming but you'll loose out on potential benefit, and you really need to compensate for it's lack (e.g. do code reviews).

Pairing is one of the core practices, dropping pairing on "simple" tasks is a slippery slope. My approach is to adopt XP by the book, for several iterations, then start tweaking iff it proves to be necessary. You're better off doing as much of XP as you possibly can.

Re: Pair programmign

Posted By:   Anonymous  
Posted On:   Saturday, June 1, 2002 12:28 AM

Shahid, do you have an example for a task where you think you wouldn't benefit from PP?

In my experience, if a (programming) task is so extremely simple that pairing gets boring, you have missed a significant opportunity to automate/generalize something.

Re: Pair programmign

Posted By:   Sebastien_Meric  
Posted On:   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.


About | Sitemap | Contact