Stuck in the back seat
My first week with pair programming has had mixed results. While the first couple of tasks came in way under the estimated time because we seem to be working twice as fast, the new guy wasn't feeling very productive. It seems that I was not giving him sufficient time and he had that "lost in the back seat" feeling.
I've read that the back-seat driver shouldn't be stuck back there all the time. We're going to aim to be driving only 50% of the time. Maybe that will make things smoother for the both of us.
The other item that is adversely affecting the pair programming experience is that we're in two different locations, me in Canada and him in the USA. As a result, our schedules don't mesh together as well as when the pair of programmers are physically in the same place. Our answer to this is to do pair programming half the time and individual tasks the other half of the time.
Overall, I think it has been going well, because I'm learning new things. Others have said that the craftsman's skill is extended by the apprentice's questions and thinking outside of the box and I definitely agree. I think this is one of the reasons why pair-programming enhances productivity.