Table of Links Abstract and I. Introduction Abstract and I. Introduction II. Related Work A. On the Existence of Pair Programming Skill A. On the Existence of Pair Programming Skill B. On the Elements of Pair Programming Skill B. On the Elements of Pair Programming Skill III. Research Method A. Research Goal and Data Collection A. Research Goal and Data Collection B. Qualitative Research Approach B. Qualitative Research Approach C. Our Notions of ‘Good’ and ‘Bad’ C. Our Notions of ‘Good’ and ‘Bad’ IV. Results A. Two Elements of Pair Programming Skill A. Two Elements of Pair Programming Skill B. Anti-Pattern: Getting Lost in the Weeds B. Anti-Pattern: Getting Lost in the Weeds C. Anti-Pattern: Losing the Partner C. Anti-Pattern: Losing the Partner D. Anti-Pattern: Drowning the Partner D. Anti-Pattern: Drowning the Partner E. Doing the Right Thing and F. Further Elements of Pair Programming Skill E. Doing the Right Thing and F. Further Elements of Pair Programming Skill V. Discussion V. Discussion VI. Summary and Future Work VI. Summary and Future Work VII. Data Availability and References VII. Data Availability and References III. RESEARCH METHOD A. Research Goal and Data Collection The overall goal of our research is to understand how ‘good’ and ‘bad’ pair programming sessions differ. Ultimately, we want to provide actionable advice for practitioners. Here, we want to understand the elements of the skill which pair programmers exhibit in successful sessions and how sessions suffer from a lack thereof. elements skill The industrial data used by Bryant et al. [4], [5] is limited to audio recordings, which makes it difficult to understand what the developers are referring to: For one out of every eight utterances, the researchers could not reconstruct what the pairs referred to [5, Sec. 5.1]. We therefore analyze industrial PP sessions comprising audio, webcam, and screencast from the PP-ind repository [15], [16], which contains a variety of over 60 everyday PP sessions from 13 companies along with pre-and post-session questionnaires filled out by the developers. Sessions from the repository have IDs like ‘CA2’ (session 2, from the first team A, at the third company C); developers are numbered similarly, e.g. ‘C2’. audio webcam screencast PP-ind Authors: (1) Franz Zieris, Institut fur Informatik, Freie Universitat, Berlin Berlin, Germany (zieris@inf.fu-berlin.de); (2) Lutz Prechelt, Institut fur Informatik. Freie Universitat Berlin, Berlin, Germany (prechelt@inf.fu-berlin.de). Authors: Authors: (1) Franz Zieris, Institut fur Informatik, Freie Universitat, Berlin Berlin, Germany (zieris@inf.fu-berlin.de); (2) Lutz Prechelt, Institut fur Informatik. Freie Universitat Berlin, Berlin, Germany (prechelt@inf.fu-berlin.de). This paper is available on arxiv under CC BY 4.0 DEED license. This paper is available on arxiv under CC BY 4.0 DEED license. available on arxiv available on arxiv