RE: OT? (RE: Pair Programming)

I may be missing your point because your 2 paragraphs seem contradictory to me. To me, "all production code written in pairs" is the same thing as "continuous code review and continuous mentoring". So then a team is either 100% committed or they are not, and the number of hours is irrelevant. How ever many hours they do is either 
   - all they need to do (at one end of the scale)
   - or is all they are able to do (because of meetings or flex time or too much (non-coding) solo or non-productive work) (at the other end of the scale).

It's a good question: "what is a lower bound on the expected time the team would spend pairing?" But assuming a 100% commitment, too low an average amount of time could indicate other problems, such as those mentioned in my 2nd bullet above. And I would put that lower bar at an average or 4 pairing hours a day (*).

(*4 hours/day once coding has started -- All projects I've been involved with began with an "inception" or "conception" or "analysis" phase in which we hadn't yet begun coding but were helping the customer enumerate the stories.) 

regards
andrew fuqua

> -----Original Message-----
> From: J. B. Rainsberger
>
> You're correct, but I had assumed that there was 100% 
> commitment to "all production code written in pairs" and that 
> coding is most of what the people had to do these days.
> 
> Perhaps my question is this: what is a lower bound on the 
> expected time the team would spend pairing? Too low an 
> average amount of time could indicate a lack of commitment to 
> continuous code review and continuous mentoring.
>


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

To unsubscribe from this group, send an email to:
extremecustomering-unsubscribe-hHKSG33TihhbjbujkaE4pw@public.gmane.org

 

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