Two Elements of Pair Programming Skill

TL;DR

This paper identifies two key elements of effective pair programming skills—maintaining Togetherness and Expediency—based on qualitative analysis of industrial sessions, highlighting behavioral patterns that influence success.

Contribution

It introduces a novel conceptual framework of pair programming skills, distinguishing them from general programming skills and emphasizing specific behavioral patterns.

Findings

Good pairs maintain Togetherness and Expediency.

Problematic behaviors include Getting Lost in the Weeds, Losing the Partner, Drowning the Partner.

Pair programming skill is distinct from general software development skill.

Abstract

Background: Pair programming (PP) can have many benefits in industry. Researchers and practitioners recognize that successful and productive PP involves some skill that might take time to learn and improve. Question: What are the elements of pair programming skill? Method: We perform qualitative analyses of industrial pair programming sessions following the Grounded Theory Methodology. We look for patterns of problematic behavior to conceptualize key elements of what 'good' and 'bad' pairs do differently. Results: Here, we report two elements of pair programming skill: Good pairs (1) manage to maintain their Togetherness and (2) keep an eye on their session's Expediency. We identify three problematic behavioral patterns that affect one or both of these elements: Getting Lost in the Weeds, Losing the Partner, and Drowning the Partner. Conclusion: Pair programming skill is separate from general software development skill. Years of PP experience are neither a prerequisite nor sufficient for successful pair programming.