DoingPairProgramming

Worried it won't look good, or your manager won't understand?

You can introduce pair programming easily without too much fuss.

1. Introduce weekly code reviews for everyone. Limit each to 1 hour. Using your own code as an example, ask for them more often ... twice weekly for 30 mins, then every day for 10 mins.

2. Rather than produce review material for these reviews, just walk through the tests. I do a 5 minute white-board diagram of the major classes, kind of like DoingAMetaphor. Encourage others to spot missing tests.

3. Ask someone to help you with your own code from time to time. Discuss the tests with them.

Soon you'll find there's always a pair doing one of the above. Someone will suggest its easier to review as you fix the tests. Its a simple next step to review as you make the next enhancement.

uh....

See also PairProgrammingChessClock for when one partner hogs the keyboard! ³host³³date³November 1, 2002³agent³Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0; .NET CLR 1.0.3705)³DoingPairProgramming