We've tried to use XP & pair programming at work. The challenge for us has been a lack of discipline in writing unit tests. This sounds like a great way of structuring things. Go and read the rest of Joe's post for more details...
...RULES: Get two developers in front of the same machine and give one of them a red hat to wear and another a green hat. Mr Red's role is to write a small unit-test that fails. In doing so, he clearly expresses the proposed interface and intention of the new code. As soon as he's happy with his failing test, he slides the keyboard over to Mrs Green. Mrs Green's intention is to do just enough work to make the test pass at which point the keyboard is passed back over to Mr Red. Repeat cycle... [Joe's Jelly]
1:51:31 PM comment ()