Interesting. We did hear complaints like this from folks starting out. What I have noticed is that when working with Pivotal veterans, those with a few years

Interesting. We did hear complaints like this from folks starting out. What I have noticed is that when working with Pivotal veterans, those with a few years under their belt, they tended to have long endurance for pairing. They also picked up tricks along the way to keep the pair engaged and allow for investigation. Maybe its like furniture movers... it takes time to build up that endurance and mastery to get to the point where it is possible to do for 3 - 4 hours at a time. Pivotal was also strict with taking 15 minute breaks... one in the AM around 10:30am and the other in the afternoon around 3pm.... but each pair can decide on their own. When I was a team lead in pairing teams, I did allow (and encouraged solo time), but the code written during solo would be consider spike code... code to learn and try stuff out. Ultimately to make it into prod code, it had to go through a pair.