Search The Blog
About this site

@RoyOsherove

Subscribe!

This site aims to connect all the dots of my online activities - from tools, books blogs and twitter accounts, to upcoming conferences, engagements and user group talks.

from 5whys.com
Twitter: @RoyOsherove
My Book: The Art of Unit Testing
Latest Posts
« [ot] Hebrew blogging attempt | Main | Solving weird problems, and making others solve them as well »
Friday
Jun042004

When people don't want to do pair programming

At one of the projects I had a chance to manage, I had to teach an entire teams (3 people) how to do pair programming. I didn't call it “Pair programming” though, as that would have brought on the FUDs, but I just made people work with each other, test-driven development style.
People seemed to be fond with the idea and have acknowledged their belief the TDD has indeed helped them a lot, but after a  while they stopped doing pair programming. When asked why arn't they working on something together they responded that “it just seems unnecessary”.
How do you respond to that? do you just let them go on without pairing? This was not a project under my control in the sense of staff, and I don't believe in forcing people to pair, because that leads to unproductive behavior. So they went on doing TDD without pairing. The code was still much better, but they definitely took more time to do it.
 
 
My point? there isn't one, really. Just wanted to share that sometimes not everything is a rose garden. be prepared.
Have you met such a situation? how did you deal with it?
 

PrintView Printer Friendly Version

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Post:
 
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>