Controlled experimentation on adaptations of pair programming

Abstract

The use of agile methods is growing in industrial practice due to the documented benefits of increased software quality, shared programmer expertise, and user satisfaction. These methods include pair programming (two programmers working side-by-side producing the code) and test-driven approaches (test cases written first to prepare for coding). In practice, software development organizations adapt agile methods to their environment. The purpose of this research is to understand better the impacts of adapting these methods. We perform a set of controlled experiments to investigate how adaptations, or variations, to the pair programming method impact programming performance and user satisfaction. We find that method variations do influence programming results. In particular, better performance and satisfaction outcomes are achieved when the pair programming is performed in face-to-face versus virtual settings, in combination with the test-driven approach, and with more experienced programmers. We also find that limiting the extent of collaboration can be effective, especially when programmers are more experienced. These experimental results provide a rigorous foundation for deciding how to adapt pair programming methods into specific project contexts.Agile software development processes are becoming increasingly viable alternatives to more disciplined, plan-driven development processes. The interest is driven by the promise of higher quality code produced in shorter periods of time, with high levels of developer satisfaction. A great deal of uncertainty remains however, on how best to structure an effective, contextspecific process that remains faithful to the principles of agility [2,5]. Few research studies report empirical results that can be used to guide project managers in these critical decisions [9,11].A key premise of agility in software development is the freedom to adapt processes and methods to the needs of a specific project. Previous research has referred to such adaptation as 'method engineering' [26,27] or 'method tailoring' [10]. Turk, France and Rumpe [30, p. 73] identify one of the central underlying assumptions of agility as ''developers have the experience needed to define and adapt their processes appropriately.'' Thus, the need for research on how to effectively adapt agile methods is clear.In this research we study the adaptation of pair programming concepts in agile development projects. We conducted a series of studies that investigate pair programming variations that are currently being employed in practice: in the work setting, preparation for coding, and extent of collaboration. Section 1 describes the pair programming method and the potential variations of the method. Existing research on pair programming is surveyed. Our research study is presented in Section 2. We perform a set of controlled

A Novel Approach for Collaborative Pair Programming

“…In others , students kept the same partner throughout the term unless unforeseen circumstances occurred. Domino et al (2007) reported better performance and satisfaction outcomes using face-to-face pair programming as compared to its virtual setting. They also found that limiting the extent of collaboration can be effective, especially when programmers are more experienced.…”

“…A traditional form of pair programming based on the driver-navigator model has been successful in many introductory computer science courses. Its success is noticeable in better performance in computer science assignments, increased team work in and outside class, enhanced learning, and decreased frustration (Cliburn, 2003;Domino, Collins, & Hevner, 2007;McDowell, Werner, Bullock, & Fernald, 2002;Nagappan et al, 2003;Sfetsos, Stamelos, Angelis, & Deligiannis, 2009;Thomas, Ratcliffe, & Robertson, 2003;VanDeGrift, 2004;Williams & Kessler, 2003;Williams, Yang, Wiebe, Ferzli, & Miller, 2002). However, pair programming has its weaknesses too (Bevan, Werner, & McDowell, 2002, Cliburn, 2003VanDeGrift, 2004).…”

An Empirical Study on the Impact of an IDE Tool Support in the Pair and Solo Programming

“…Essentially, the observer reviews the work for possible defects, writes down notes, or defines strategies for solving any issue that can arise in the task that they are working on. Various empirical studies that report beneficial effects of the use of this practice have been conducted [10][11][12][13][14][15][16][17][18][19][20][21][22][23][24]. Some beneficial effects reported in these studies are that pair programming helps to produce shorter programs and achieve better designs; programs contain fewer defects than do those written individually, and pairs usually require less time to complete a task than do programmers working individually.…”

Effects of Solo and Pair Programming Instructional Strategies on Students’ Academic Achievement in Visual-Basic.Net Computer Programming Language

“…The navigator is expected to detect errors made by the driver and offer ideas in solving problems. Pair programming, first used in 1999 as one of the core practices in the Extreme Programming (XP) software development methodology in industry, has been widely implemented in industry as well as in educational settings [2,3]. Particularly in educational settings, researchers and academics had previously applied pair programming techniques in the fields of software engineering (SE) and computer science (CS).…”