[Arisholm et al. 2007] Arisholm, E., H. Gallis, T. Dybå, and D. Sjøberg. 2007. Evaluating Pair Programming with Respect to System Complexity and Programmer Expertise. IEEE Transactions in Software Engineering 33(2): 65–86.

[Baheti et al. 2002a] Baheti, P., E. Gehringer, and D. Stotts. 2002. Exploring the Efficacy of Distributed Pair Programming. In Lecture Notes in Computer Science, volume 2418: Extreme Programming and Agile Methods – XP/Agile Universe 2002, ed. D. Wells and L. Williams, 208–220. Berlin: Springer-Verlag.

[Baheti et al. 2002b] Baheti, P., L. Williams, E. Gehringer, and D. Stotts. 2002. Exploring Pair Programming in Distributed Object-Oriented Team Projects. Paper presented at the 11th OOPSLA Educators’ Symposium, November 4–8, in Seattle, WA.

[Beck 2005] Beck, K. 2005. Extreme Programming Explained: Embrace Change, Second Edition. Reading, MA: Addison-Wesley.

[Begel and Nagappan 2008] Begel, A., and N. Nagappan. 2008. Pair programming: What’s in it for me? Proceedings of the ACM-IEEE international symposium on empirical software engineering and measurement: 120–128.

[Belshee 2005] Belshee, A. 2005. Promiscuous pairing and beginner’s mind: embrace inexperience. Proceedings of the Agile Development Conference: 125–131.

[Berenson et al. 2005] Berenson, S.B., L. Williams, and K.M. Slaten. 2005. Using Pair Programming and Agile Development Methods in a University Software Engineering Course to Develop a Model of Social Interactions. Paper presented at Crossing Cultures, Changing Lives Conference, July 31–August 3, in Oxford, UK.

[Braught et al. 2008] Braught, G., L.M. Eby, and T. Wahls. 2008. The effects of pair-programming on individual programming skill. Proceedings of the 39th SIGCSE technical symposium on computer science education: 200–204.

[Brooks 1975] Brooks, F.P. 1975. Mythical Man-Month: Essays on Software Engineering. Reading, MA: Addison-Wesley.

[Carver et al. 2007] Carver, J., L. Henderson, L. He, J. Hodges, and D. Reese. 2007. Increased Retention of Early Computer Science and Software Engineering Students Using Pair Programming. Proceedings of the 20th Conference on Software Engineering Education and Training: 115–122.

[Chao and Atli 2006] Chao, J., and G. Atli. 2006. Critical personality traits in successful pair programming. Proceedings of the conference on AGILE 2006: 89–93.

[Chong and Hurlbutt 2007] Chong, J and T. Hurlbutt. 2007. The Social Dynamics of Pair Programming. Proceedings of the 29th International Conference on Software Engineering: 354–363.

[Cicirello 2009] Cicirello, V.A. 2009. On self-selected pairing in CS1: who pairs with whom? Journal of Computing Sciences in Colleges 24(6): 43–49.

[Constantine 1995] Constantine, L.L. 1995. Constantine on Peopleware. Englewood Cliffs, NJ: Yourdon Press.

[Coplien 1995] Coplien, J.O. 1995. A Development Process Generative Pattern Language. In Pattern Languages of Program Design, ed. James O. Coplien and Douglas C. Schmidt, 183–237. Reading, MA: Addison-Wesley.

[Coplien and Harrison 2005] Coplien, J.O., and N.B. Harrison. 2005. Organizational Patterns of Agile Software Development. Upper Saddle River, NJ: Pearson Prentice-Hall.

[Devide et al. 2008] Devide, J.V.S., A. Meneely, C.-W. Ho, L. Williams, and M. Devetsikiotis. 2008. Jazz Sangam: A Real-Time Tool for Distributed Pair Programming on a Team Development Platform. Paper presented at the First International Workshop on Infrastructure for Research in Collaborative Software Engineering, November 9, in Atlanta, GA.

[Dybå et al. 2007] Dybå, T., E. Arisholm, D. Sjøberg, J. Hannay, and F. Shull. 2007. Are Two Heads Better Than One? On the Effectiveness of Pair Programming. IEEE Software 24(6): 12–15.

[Edwards et al. 2010] Edwards, R.L., J.K. Stewart, and M. Ferati. 2010. Assessing the effectiveness of distributed pair programming for an online informatics curriculum. Inroads 1(1): 48–54.

[Erdogmus and Williams 2003] Erdogmus, H., and L. Williams. 2003. The Economics of Software Development by Pair Programmers. The Engineering Economist 48(4): 283–319.

[Fagan 1986] Fagan, M.E. 1986. Advances in Software Inspection. IEEE Transactions on Software Engineering 12(7): 744–751.

[Flor 2006] Flor, N. 2006. Globally Distributed Software Development and Pair Programming. Communications of the ACM 49(10): 57–58.

[Freudenberg et al. 2007] Freudenberg, S., P. Romero, and B. du Boulay. 2007. “Talking the talk”: Is intermediate-level conversation the key to the pair programming success story? Proceedings of AGILE 2007: 84–91.

[Frever and Ingalls 2006] Frever, T., and P. Ingalls. 2006. The pairing session as the atomic unit of work. Proceedings of the Conference on AGILE 2006: 165–169.

[Fronza et al. 2009] Fronza, I., A. Sillitti, and G. Succi. 2009. An interpretation of the results of the analysis of pair programming during novices integration in a team. Proceedings of the 3rd International Symposium on Empirical Software Engineering and Measurement: 225–235.

[Grant Braught and Wahls 2010] Grant Braught, J.M. and Tim Wahls. 2010. The benefits of pairing by ability. Proceedings of the 41st ACM technical symposium on computer science education: 249–253.

[Hanks 2005] Hanks, B. 2005. Student Performance in CS1 with Distributed Pair Programming. Proceedings of the 10th Annual SIGCSE Conference on Innovation and Technology in Computer Science Education: 316–320.

[Hanks 2007] Hanks, B. 2007. Problems Encountered by Novice Pair Programmers. Proceedings of the Third International Workshop on Computing Education Research: 159–164.

[Hannay et al. 2010] Hannay, J.E., E. Arisholm, H. Engvik, and D.I.K. Sjøberg. 2010. Effects of Personality on Pair Programming. IEEE Transactions on Software Engineering 36(1): 61–80.

[Ho et al. 2004] Ho, C-w., S. Raha, E. Gehringer, and L. Williams. 2004. Sangam: A Distributed Pair Programming Plug-in for Eclipse. Proceedings of the 2004 OOPSLA workshop on Eclipse technology eXchange: 73–77.

[Höfer 2008] Höfer, A. 2008. Video Analysis of Pair Programming. Proceedings of the 2008 International Workshop on Scrutinizing Agile Practices:37–41.

[Hulkko and Abrahamsson 2005] Hulkko, H., and P. Abrahamsson. 2005. A Multiple Case Study on the Impact of Pair Programming on Product Quality. Proceedings of the 27th International Conference on Software Engineering: 495–504.

[Jacobson and Schaefer 2008] Jacobson, N., and S.K. Schaefer. 2008. Pair programming in CS1: overcoming objections to its adoption. SIGCSE Bulletin 40(2): 93–96.

[Jensen 2003] Jensen, R. 2003. A Pair Programming Experience. CrossTalk 16(3): 22–24.

[Joseph and Payne 2003] Joseph, A., and M. Payne. 2003. Group Dynamics and Collaborative Group Performance. Proceedings of the 34th SIGCSE Technical Symposium on Computer Science Education: 368–371.

[Lacey 2006] Lacey, M. 2006. Adventures in Promiscuous Pairing: Seeking Beginner’s Mind. Proceedings of the conference on AGILE 2006: 263–269.

[Layman 2006] Layman, L. 2006. Changing Students’ Perceptions: An Analysis of the Supplementary Benefits of Collaborative Software Development. Proceedings of the 19th Conference on Software Engineering Education and Training: 156–166.

[Layman et al. 2005] Layman, L., L. Williams, J. Osborne, S. Berenson, K. Slaten, and M. Vouk. 2005. How and Why Collaborative Software Development Impacts the Software Engineering Course. Proceedings of the 35th Annual Conference on Frontiers in Education: T4C 9–14.

[Luck 2004] Luck, G. 2004. Subclassing XP: Breaking its rules the right way. Proceedings of the Agile Development Conference 2004: 114–119.

[McDowell et al. 2002] McDowell, C., L. Werner, H. Bullock, and J. Fernald. 2002. The Effects of Pair Programming on Performance in an Introductory Programming Course. Proceedings of the 33rd SIGCSE technical symposium on computer science education: 38–42.

[McDowell et al. 2003] McDowell, C., L. Werner, H. Bullock, and J. Fernald. 2003. The Impact of Pair Programming on Student Performance, Perception, and Persistence. Proceedings of the 25th International Conference on Software Engineering: 602–607.

[McDowell et al. 2006] McDowell, C., L. Werner, H. Bullock, and J. Fernald. 2006. Pair Programming Improves Student Retention, Confidence, and Program Quality. Communications of the ACM 49(8): 90–95.

[Mendes et al. 2006] Mendes, E., L. Al-Fakhri, and A. Luxton-Reilly. 2006. A Replicated Experiment of Pair Programming in a 2nd Year Software Development and Design Computer Science Course. Proceedings of the 11th Annual SIGCSE Conference on Innovation and Technology in Computer Science Education: 108–112.

[Mujeeb-u-Rehman et al. 2005] Mujeeb-u-Rehman, M., X. Yang, J. Dong, and M. Abdul Ghafoor. 2005. Heterogeneous and homogenous pairs in pair programming: an empirical analysis. Proceedings of the Canadian Conference on Electrical and Computer Engineering 2005: 1116–1119.

[Nagappan et al. 2003] Nagappan, N., L. Williams, M. Ferzli, K. Yang, E. Wiebe, C. Miller, and S. Balik. 2003. Improving the CS1 Experience with Pair Programming. Proceedings of the 34th SIGCSE technical symposium on computer science education: 359–362.

[Natsu et al. 2003] Natsu, H., J. Favela, A. Morán, D. Decouchant, and A. Martinez-Enriquez. 2003. Distributed Pair Programming on the Web. Proceedings of the 4th Mexican International Conference on Computer Science: 81–88.

[Navoraphan et al. 2006] Navoraphan, K., E. F. Gehringer, J. Culp, K. Gyllstrom, and D. Stotts. 2006. Next-generation DPP with Sangam and Facetop. Proceedings of the 2006 OOPSLA workshop on Eclipse technology eXchange: 6–10.

[Nawrocki and Wojciechowski 2001] Nawrocki, J., and A. Wojciechowski. 2001. Experimental Evaluation of Pair Programming. Proceedings of the 12th European Software Control and Metrics Conference: 269–276.

[Nosek 1998] Nosek, J.T. 1998. The Case for Collaborative Programming. Communications of the ACM 41(3): 105–108.

[Oblinger 2003] Oblinger, D. 2003. Boomers, Gen-Xers, and Millennials: Understanding the New Students. Educause Review 38(4): 37–47.

[Pandey et al. 2003] Pandey, A., C. Miklos, M. Paul, N. Kameli, F. Boudigou, V. Vijay, A. Eapen, I. Sutedjo, and W. Mcdermott. 2003. Application of tightly coupled engineering team for development of test automation software—a real world experience. Proceedings of the 27th Annual International Computer Software and Applications Conference: 56–63.

[Phongpaibul and Boehm 2006] Phongpaibul, M., and B. Boehm. 2006. An Empirical Comparison Between Pair Development and Software Inspection in Thailand. Proceedings of the 2006 ACM/IEEE International Symposium on Empirical Software Engineering: 85–94.

[Salleh et al. 2009] Salleh, N., E. Mendes, J. Grundy, and G.S.J. Burch. 2009. An empirical study of the effects of personality in pair programming using the five-factor model. Proceedings of the 2009 3rd International Symposium on Empirical Software Engineering and Measurement: 214–225.

[Schwaber and Beedle 2002] Schwaber, K., and M. Beedle. 2002. Agile Software Development with SCRUM. Upper Saddle River, NJ: Prentice-Hall.

[Sennett and Sherriff 2010] Sennett, J., and M. Sherriff. 2010. Compatibility of Partnered Students in Computer Science Education. 41st ACM Technical Symposium on Computer Science Education (SIGCSE): 244‒248.

[Simon and Hanks 2007] Simon, B., and B. Hanks. 2007. First Year Students’ Impressions of Pair Programming in CS1. Proceedings of the Third International Workshop on Computing Education Research: 73–86.

[Slaten et al. 2005] Slaten, K.M., M. Droujkova, S. Berenson, L. Williams, and L. Layman. 2005. Undergraduate Student Perceptions of Pair Programming and Agile Software Methodologies: Verifying a Model of Social Interaction. Proceedings of the Agile Conference 2005: 323–330.

[Srikanth et al. 2004] Srikanth, H., L. Williams, E. Wiebe, C. Miller, and S. Balik. 2004. On Pair Rotation in the Computer Science Course. Proceedings of the 17th Conference on Software Engineering Education and Training: 144–149.

[Succi et al. 2002] Succi, G., M. Marchesi, W. Pedrycz, and L. Williams. 2002. Preliminary analysis of the effects of pair programming on job satisfaction. Proceedings of the Fourth International Conference on eXtreme Programming and Agile Processes in Software: 212–215.

[Van Toll et al. 2007] Van Toll, T., III, T., R. Lee, and T. Ahlswede. 2007. Evaluating the Usefulness of Pair Programming in a Classroom Setting. Proceedings of the 6th IEEE/ACIS International Conference on Computer and Information Science (ICIS) 2007: 302–308.

[Vanhanen and Korpi 2007] Vanhanen, J., and H. Korpi. 2007. Experiences of Using Pair Programming in an Agile Project. Proceedings of the 40th Annual Hawaii International Conference on System Sciences (HICSS) 2007: 274b.

[Vanhanen and Lassenius 2007] Vanhanen, J., and C. Lassenius. 2007. Perceived Effects of Pair Programming in an Industrial Context. Proceedings of the 33rd EUROMICRO Conference on Software Engineering and Advanced Applications: 211–218.

[Vanhanen et al. 2007] Vanhanen, J., C. Lassenius, and M. Mäntylä. 2007. Issues and Tactics when Adopting Pair Programming: A Longitudinal Case Study. Proceedings of the International Conference on Software Engineering Advances (ICSEA) 2007: 70.

[Walle and Hannay 2009] Walle, T., and J.E. Hannay. 2009. Personality and the nature of collaboration in pair programming. Proceedings of the 2009 3rd International Symposium on Empirical Software Engineering and Measurement: 203–213.

[Williams 2000] Williams, L. A. 2000. The Collaborative Software Process. PhD diss., University of Utah.

[Williams and Kessler 2000] Williams, L. A. and R. R. Kessler. 2000. All I Ever Needed to Know About Pair Programming I Learned in Kindergarten. Communications of the ACM. 43(5): 108–114.

[Williams and Kessler 2003] Williams, L., and R. Kessler. 2003. Pair Programming Illuminated. Reading, MA: Addison-Wesley.

[Williams and Layman 2007] Williams, L,. and L. Layman. 2007. Lab Partners: If They’re Good Enough for the Natural Sciences, Why Aren’t They Good Enough for Us? Proceedings of the 20th Conference on Software Engineering Education and Training: 72–82.

[Williams et al. 2000] Williams, L., R. Kessler, W. Cunningham, and R. Jeffries. 2000. Strengthening the Case for Pair-Programming. IEEE Software 17(4):19–25.

[Williams et al. 2002] Williams, L., E. Wiebe, K. Yang, M. Ferzli, and C. Miller. 2002. In Support of Pair Programming in the Introductory Computer Science Course. Computer Science Education 12(3):197–212.

[Williams et al. 2003] Williams, L., C. McDowell, N. Nagappan, J. Fernald, and L. Werner. 2003. Building Pair Programming Knowledge Through a Family of Experiments. Proceedings of the 2003 International Symposium on Empirical Software Engineering: 143–152.

[Williams et al. 2004a] Williams, L., W. Krebs, L. Layman, A. Antón, and P. Abrahamsson. 2004. Toward a Framework for Evaluating Extreme Programming. Proceedings of Empirical Assessment in Software Eng. (EASE) 2004: 11–20.

[Williams et al. 2004b] Williams, L., A. Shukla, and A. Antón. 2004. An Initial Exploration of the Relationship Between Pair Programming and Brooks’ Law. Proceedings of the Agile Development Conference 2004: 11–20.

[Williams et al. 2006] Williams, L., L. Layman, J. Osborne, and N. Katira. 2006. Examining the Compatibility of Student Pair Programmers. Proceedings of the Conference on Agile 2006: 411–420.

[Wray 2010] Wray, S. 2010. How Pair Programming Really Works. IEEE Software 27(1): 50–55.

[Xu and Rajlich 2005] Xu, S., and V. Rajlich. 2005. Pair Programming in Graduate Software Engineering Course Projects. Proceedings of the 35th Annual Frontiers in Education Conference: F1G7–F1G12.