What does pair programming look like for your team?

Jonathan Carter - May 12 '19 - - Dev Community

Hey All! I’m curious to know whether your team does pair programming of any form (let’s not get too academic!), and if so, what exactly it looks like. For example:

  1. How frequently do you do it? Daily? Weekly? Full-time?

  2. How long do pairing sessions usually last? An hour? Three hours?

  3. Are sessions initiated on an ad-hoc basis (e.g. you just ping someone on Slack), or do you schedule/plan them ahead of time? (e.g. you decide to pair with someone on a task as part of sprint planning)

  4. Do you only ever do two-person pairing sessions? Or do you ever have three or more people collaborating? (Mob programming/swarming)

  5. Do you typically pair with the same people? Are they remote or co-located with you?

  6. What is the typical scope of task you pair on? A bug? A user story? Prototyping?

  7. What is the typical motivation for doing pairing sessions? Knowledge transfer/shared ownership? Mentoring? Code review?

  8. Does you and your pair have specific roles during the session? (e.g. driver, navigator). Or do you keep things fairly informal?

  9. Do you use any sort of time management techniques to add structure to the session (e.g. pomodoro)?

That’s obviously a bunch of questions, so feel free to share as much or as little as is convenient. Additionally, if you’ve already written a blog post about your workflow, then just share a link to that. No need to repeat yourself! 🤗

As part of building out Visual Studio Live Share, I’ve had the opportunity to learn from a ton of teams regarding how they collaborate. However, I’m increasingly inspired by the broader DEV community, and so I’d love to hear what’s actually working well for folks in-the-wild 🙌

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terabox Video Player