Re: "Winning" the pair programming discussion

Hi,

there is growing empirical evidence that pair programming results in lower 
costs both during development and after deployment.   the former comes from 
reduced testing costs due to higher quality initial code; the latter from 
the lower maintenance costs that come with a better quality product.

also, although the first times an organization uses pair programming result 
in a greater number of hours required to complete a task. as pair 
experience increases the total hours approaches the same value consumed by 
the "traditional" approach.

regardless of whether refactoring renders one "expert's" specific knowledge 
out of date, pairing does spread knowledge around and protect the project's 
intellectual investment.  it also does help programmers acquire new skills 
and experiences.

pair programming may require the investment of a few projects, but with the 
payoff being lowered development AND maintenance costs, plus smarter and 
more accomplished programmers, it should be worth a look.

pat




------------------------ Yahoo! Groups Sponsor ---------------------~-->
Get 128 Bit SSL Encryption!
http://us.click.yahoo.com/LIgTpC/vN2EAA/xGHJAA/nhFolB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
[email protected]

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/