I have done the "two programmers, one terminal" approach advocated by Beck for XP developments (not just TDD) and it worked well. We delivered on time with all features present and correct (where correct means the application passed the customers Business Acceptance Tests - first time).
I should note we were both quite experienced developers, and I would say we were quite close in ability. It was just the two of us, not a revolving team of 5 or 6, but I could easily see that working too, if you havre the right people. We didn't do pair programming the whole time - it was more prevalent during the early weeks of the project, when we were developing the important parts of the framework. Later on we tended to separate to our own workstations to complete more mundane requirements. Try it - it is a hard discipline to maintain, but if you can achieve some success , it is naturally reinforcing. If you struggle to get the approach to work, step back and try to see what is holding you back L -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Sunday, 2 April 2006 10:05 AM To: perl-qa@perl.org Subject: [OT] TDD + Pair Programming I have never actually had an opportunity to practice this, but I've always felt that the most obvious way to combine test-driven development with pair programming was to have one person write test code while the other person writes application code. Presumably they might change roles periodically, but I'm not sure if they would actually work at the same terimnal. However, I've never heard anyone excplicitly advocate for this approach. Is this actually happening and I'm just not aware of it? Or is there some obstacle to this approach that I haven't considered? -Jeff __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ********************************************************************** IMPORTANT The contents of this e-mail and its attachments are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you received this e-mail in error, please notify the HPA Postmaster, [EMAIL PROTECTED], then delete the e-mail. This footnote also confirms that this e-mail message has been swept for the presence of computer viruses by Ironport. Before opening or using any attachments, check them for viruses and defects. Our liability is limited to resupplying any affected attachments. HPA collects personal information to provide and market our services. For more information about use, disclosure and access see our Privacy Policy at www.hpa.com.au **********************************************************************
