Although pair programming is becoming more prevalent in software development, and a number of reports have been written about it [4] [6], few have addressed the manner in which pairing actually takes place [5]. Even fewer consider the methods employed to manage issues such as role change or the communication of complex issues. Here we contribute by highlighting the way resources designed for individuals are re-appropriated and augmented to facilitate pair collaboration.

Despite sparse and sometimes contradictory evidence, eXtreme programming (XP) is currently growing in popularity as an alternative strategy for developing software. This paper proposes a methodology for observational studies of one of XPs twelve practices, pair programming, including the analysis of verbalisations, interactions and artefacts in order to improve our understanding of its cognitive implications. In addition, a protocol for analysing pair programming behaviours is included as a means of identifying the behavioural differences of those who are more expert or novice at pair programming and understanding the effect of pairing programmers of differing expertise. Initial results from a recent study using this methodology are then presented