Advertisement

A Framework for Understanding the Factors Influencing Pair Programming Success

  • Mustafa Ally
  • Fiona Darroch
  • Mark Toleman
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3556)

Abstract

Pair programming is one of the more controversial aspects of several Agile system development methods, in particular eXtreme Programming (XP). Various studies have assessed factors that either drive the success or suggest advantages (and disadvantages) of pair programming. In this exploratory study the literature on pair programming is examined and factors distilled. These factors are then compared and contrasted with those discovered in our recent Delphi study of pair programming. Gallis et al. (2003) have proposed an initial framework aimed at providing a comprehensive identification of the major factors impacting team programming situations including pair programming. However, this study demonstrates that the framework should be extended to include an additional category of factors that relate to organizational matters. These factors will be further refined, and used to develop and empirically evaluate a conceptual model of pair programming (success).

Keywords

Delphi Study Initial Framework Pair Programming Agile Software Development IEEE Software 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Baer, M.: The New X-Men, viewed 1/12/04 (2003), http://www.wired.com/wired/archive/11.09/xmen.html?pg=1&topic=&topics
  2. 2.
    Beck, K.: Extreme Programming Explained: Embrace Change. Addison Wesley, Boston (1999)Google Scholar
  3. 3.
    Brooks, F.P.: The Mythical Man-Month Essays on Software Engineering, Anniversary Edn. Addison-Wesley, Boston (1995)Google Scholar
  4. 4.
    Cockburn, A., Williams, L.: The Costs and Benefits of Pair Programming. In: Proceedings of XP 2000, Sardinia, Italy, June 2-23 (2000)Google Scholar
  5. 5.
    Day, L.: Delphi Research in the Corporate Environment. In: Linstone, Turoff (eds.) The Delphi Method: Techniques and Applications, Addison-Wesley, London (1975)Google Scholar
  6. 6.
    Dick, A.J., Zarnett, B.: Paired Programming and Personality Traits. In: Proceedings of XP 2002, Sardinia, Italy, May 26–29, pp. 82-85 (2002)Google Scholar
  7. 7.
    Flies, D.D.: Is Pair Programming a Valuable Practice?, viewed 6/12/04(2003), http:// csci. mrs.umn.edu/UMMCSciWiki/pub/CSci3903s03/StudentPaperMaterials/ flies-pairprogramming03.pdf Google Scholar
  8. 8.
    Gallis, H., Arisholm, E., Dybå, T.: An Initial Framework for Research on Pair Programming. In: Proceedings of the 2003 International Symposium on Empirical Software Engineering-ISESE 2003, pp. 132–142 (2003)Google Scholar
  9. 9.
    Glass, R.L.: Software Runaways. Prentice Hall, New Jersey (1998)Google Scholar
  10. 10.
    Grenning, J.: Launching Extreme Programming at a Process-Intensive Company. IEEE Software 18(6), 27–33 (2001)CrossRefGoogle Scholar
  11. 11.
    Hanks, B.: Empirical Studies of Pair Programming. In: 2nd International Workshop on Empirical Evaluation of Agile Processes, New Orleans, Louisiana (2003)Google Scholar
  12. 12.
    Jensen, R.W.: A Pair Programming Experience. Journal of Defense Software Engineering, March, viewed 1/12/04 (2003), http://www.stsc.hill.af.mil/crosstalk/2003/03/jensen.html
  13. 13.
    Lui, K.M., Chan, K.C.C.: When Does a Pair Outperform Two Individuals. In: Marchesi, M., Succi, G. (eds.) XP 2003. LNCS, vol. 2675, pp. 225–233. Springer, Heidelberg (2003)CrossRefGoogle Scholar
  14. 14.
    Napier, R.W., Gershenfeld, M.: Groups: Theory and experience, 6th edn. Houghton Mifflin Company, Boston (1999)Google Scholar
  15. 15.
    Poole, C., Huisman, J.W.: Using Extreme Programming in a Maintenance Environment. IEEE Software 18(6), 42–50 (2001)CrossRefGoogle Scholar
  16. 16.
    Pulugurtha, S., Neveu, J., Lynch, F.: Extreme Programming in a Customer Services Organization. In: Proceedings of XP 2002, Sardinia, Italy, May 26–29, pp. 193-194 (2002)Google Scholar
  17. 17.
    Rowe, G., Wright, G., Bolger, F.: Delphi: A Reevaluation of Research and Theory. Technological Forecasting and Social Change 39(3), 235–251 (1991)CrossRefGoogle Scholar
  18. 18.
    Sharifabdi, K., Grot, C.: Team Development and Pair Programming – Tasks and Challenges of the XP Coach. In: Proceedings of XP 2002, Sardinia, Italy, May 26-29, pp. 166-169 (2002)Google Scholar
  19. 19.
    Toleman, M., Ally, M., Darroch, F.: A Delphi Study of Pair Programming, Working paper, Department of Information Systems, University of Southern Queensland (2005) Google Scholar
  20. 20.
    Wiki: viewed 1/12/04 (2004), http://c2.com/cgi/wiki?PairProgramming
  21. 21.
    Williams, L.: The Collaborative Software Process, unpublished PhD dissertation, Department of Computer Science, University of Utah (2000) Google Scholar
  22. 22.
    Williams, L., Kessler, R.: Pair Programming Illuminated. Addison-Wesley, Boston (2002)Google Scholar
  23. 23.
    Williams, L., Kessler, R.R., Cunningham, W., Jeffries, R.: Strengthening the Case for Pair Programming. IEEE Software 17(4), 19–25 (2000)CrossRefGoogle Scholar
  24. 24.
    Yourdon, E.: Death March: The Complete Developer’s Guide to Surviving Mission Impossible’ Projects. Prentice Hall, New Jersey (1999)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2005

Authors and Affiliations

  • Mustafa Ally
    • 1
  • Fiona Darroch
    • 1
  • Mark Toleman
    • 1
  1. 1.Department of Information SystemsUniversity of Southern QueenslandToowoombaAustralia

Personalised recommendations