Software-Related Intel

Pomo-pairo : Pomodoro Technique + Pairing

Recently, another Obtivian, Scott Parker, joined my team at a client. Since this meant we’d be pairing a lot, I thought we should experiment and see how the Pomodoro Technique worked for us pairing. Overall, I’ve really enjoyed using it and wanted to share some of my thoughts.

Disclaimer - When it comes to productivity boosting techniques, I’m not dogmatic. Instead, I’ll figure out the core ideas and fit them into my work flow comfortably. Try, assess, and adjust.

The Good

• Reducing broken pairs - Pair-programming works best with both people there…blew your mind, didn’t I? As silly as this seems to point out, pairing loses value when team members are taking breaks at different times (e.g- grabbing snacks, bathroom breaks). Having a visible indication of the next approaching break encourages the pair to power through.
• Break checks - It’s easy to lose track of time during a break (“I have time to check twitter quick…”). With both team members aware of the break duration, they can keep each-other in check. A quick “ready when you are” at the end of a break reminds the other it’s time to rock.
• Progressive burn - Pairing is exhausting. Even when you’re not driving, you’re constantly communicating, thinking about design, and proofing your pair’s work. The paced nature of the work/break cycle leads to a steady daily-burn. It’s easy to lose track of time pairing. Cranking through a problem and ignoring breaks seems productive, but I’ve noticed it leaves me mentally fatigued earlier in the day.

Some Challenges

• Inconsistent availability - If the person you pair with has a drastically different schedule than you, the Pomodoro Technique can fall short. Recently, I worked on a project where the other developer frequently had administrative meetings that would cut through large coding blocks. If he only had a one hour block to code, I’d prefer to just pair the entire block.
• Interruptions - This isn’t pairing specific, rather a frequent issue I have using the Pomodoro Technique at work. The bread and butter of a pomodoro is that it’s dedicated, uninterrupted work. However, not every member of the team understands how detrimental context switching is to productivity. I have no problem putting off an email or IM till a break. However, I have a hard time waving off an approaching teammate without feeling like a jerk.

So far, it’s been working well for us. I recommend giving it a try. Experiment. Tweak. And if it’s not working, drop it.