Pair programming effectiveness is determined by specific skills rather than mere physical proximity. Two critical elements of pair programming skill include Maintaining Togetherness and focusing on Expediency. Three problematic behaviors hinder effective pair programming: Getting Lost in the Weeds leads to irrelevant discussions; Losing the Partner occurs when one member monopolizes the task; and Drowning the Partner happens when one member overwhelms the other with excessive information. Existing data consists of brief snapshots, indicating a need for longitudinal studies to thoroughly understand the factors influencing pair programming dynamics.
Pair programming (PP) does not just 'work' because two software developers sit next to each other. Developers can be more or less skilled at pair programming.
We characterize two elements of that skill that are independent from software development skills: Maintaining Togetherness and keeping an eye on Expediency.
Three patterns of problematic behavior were described: Getting Lost in the Weeds, Losing the Partner, and Drowning the Partner, which impact the effectiveness of pair programming.
Current data is limited to snapshots of behavior; longitudinal research is needed to understand the influence of developers' personal styles and their experiences.
Collection
[
|
...
]