Confirming the influence of educational background in pair-design knowledge through experiments

The sharing of tacit knowledge is a strategic factor for the success of software process, from a number of perspectives: training, project assimilation, and reducing noise in knowledge transfer. Pair programming is supposed to be a practice suitable for this purpose. Unfortunately, the building of tacit knowledge is determined by factors that are difficult to isolate and capture because they concern personal attitude and capability. Thus, we have focused on the possible causes forming the individual ability, that can be isolated and studied, such as the individual education background. We have applied the practice of working in pairs to the design phase. We have made an experiment and a replica in academic environment, in order to understand the relationship between the building of knowledge through the practice and the individual background. In this paper we discuss the replica and compare the results with the first experiment's ones.

[1]  Aniello Cimitile,et al.  Working in pairs as a means for design knowledge building: an empirical study , 2004, Proceedings. 12th IEEE International Workshop on Program Comprehension, 2004..

[2]  Kent L. Beck,et al.  Extreme programming explained - embrace change , 1990 .

[3]  Laurie A. Williams,et al.  The effects of "pair-pressure" and "pair-learning" on software engineering education , 2000, Thirteenth Conference on Software Engineering Education and Training.

[4]  Robert R. Kessler,et al.  The collaborative software process(sm) , 2000 .

[5]  Jeffrey C. Carver,et al.  Using Empirical Studies during Software Courses , 2003, ESERNET.

[6]  Laurie A. Williams,et al.  Strengthening the Case for Pair Programming , 2000, IEEE Softw..

[7]  Laurie A. Williams,et al.  An initial exploration of the relationship between pair programming and Brooks' law , 2004, Agile Development Conference.

[8]  Shari Lawrence Pfleeger,et al.  Preliminary Guidelines for Empirical Research in Software Engineering , 2002, IEEE Trans. Software Eng..

[9]  Charles E. McDowell,et al.  The effects of pair-programming on performance in an introductory programming course , 2002, SIGCSE '02.

[10]  Tammy VanDeGrift.  Coupling pair programming and writing: learning about students' perceptions and processes , 2004, SIGCSE.

[11]  Claes Wohlin,et al.  Using Students as Subjects—A Comparative Study of Students and Professionals in Lead-Time Impact Assessment , 2000, Empirical Software Engineering.

[12]  Grigori Melnik,et al.  Direct verbal communication as a catalyst of agile knowledge sharing , 2004, Agile Development Conference.

[13]  Jr. Frederick P. Brooks,et al.  The mythical man-month (anniversary ed.) , 1995 .

[14]  Adam Wojciechowski,et al.  Experimental Evaluation of Pair Programming , 2001 .

[15]  Fred P. Brooks,et al.  The Mythical Man-Month , 1975, Reliable Software.

[16]  Aniello Cimitile,et al.  Lessons learned about distributed pair programming: what are the knowledge needs to address? , 2003, WET ICE 2003. Proceedings. Twelfth IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises, 2003..

[17]  Forrest Shull,et al.  Building Knowledge through Families of Experiments , 1999, IEEE Trans. Software Eng..

[18]  Tammy VanDeGrift.  Coupling pair programming and writing: learning about students' perceptions and processes , 2004 .

[19]  Laurie A. Williams,et al.  In support of student pair-programming , 2001, SIGCSE '01.