Role of collective ownership and coding standards in coordinating expertise in software project teams

Software development is a complex undertaking that continues to present software project teams with numerous challenges. Software project teams are adopting extreme programming (XP) practices in order to overcome the challenges of software development in an increasingly dynamic environment. The ability to coordinate software developers' efforts is critical in such conditions. Expertise coordination has been identified as an important emergent process through which software project teams manage non-routine challenges in software development. However, the extent to which XP enables software project teams to coordinate expertise is unknown. Drawing on the agile development and expertise coordination literatures, we examine the role of collective ownership and coding standards as processes and practices that govern coordination in software project teams. We examine the relationship between collective ownership, coding standards, expertise coordination, and software project technical quality in a field study of 56 software project teams comprising 509 software developers. We found that collective ownership and coding standards play a role in improving software project technical quality. We also found that collective ownership and coding standards moderated the relationship between expertise coordination and software project technical quality, with collective ownership attenuating the relationship and coding standards strengthening the relationship. Theoretical and practical implications of the findings are discussed.

[1]  Brian Fitzgerald,et al.  Software development method tailoring at Motorola , 2003, CACM.

[2]  Detmar W. Straub,et al.  Validating Instruments in MIS Research , 1989, MIS Q..

[3]  Wai Fong Boh,et al.  Expertise and Collaboration in the Geographically Dispersed Organization , 2007, Organ. Sci..

[4]  Craig Larman,et al.  Agile and Iterative Development: A Manager's Guide , 2003 .

[5]  Wanda J. Orlikowski,et al.  Research Commentary: Desperately Seeking the "IT" in IT Research - A Call to Theorizing the IT Artifact , 2001, Inf. Syst. Res..

[6]  Kathleen M. Carley,et al.  The Contingent Effects of Transactive Memory: When Is It More Beneficial to Know What Others Know? , 2006, Manag. Sci..

[7]  James D. Herbsleb,et al.  Familiarity, Complexity, and Team Performance in Geographically Distributed Software Development , 2007, Organ. Sci..

[8]  Rajiv D. Banker,et al.  The Moderating Effects of Structure on Volatility and Complexity in Software Enhancement , 2000, Inf. Syst. Res..

[9]  R. Moreland,et al.  Exploring the Performance Benefits of Group Training: Transactive Memory or Improved Communication? , 2000 .

[10]  Even-André Karlsson,et al.  Daily build and feature development in large distributed projects , 2000, Proceedings of the 2000 International Conference on Software Engineering. ICSE 2000 the New Millennium.

[11]  Raymond R. Panko,et al.  Applying Code Inspection to Spreadsheet Testing , 1999, J. Manag. Inf. Syst..

[12]  Kieran Conboy,et al.  Agility from First Principles: Reconstructing the Concept of Agility in Information Systems Development , 2009, Inf. Syst. Res..

[13]  野中 郁次郎,et al.  The knowledge-creating company , 2008 .

[14]  B. Bahli,et al.  The role of knowledge creation in adopting extreme programming model: an empirical study , 2005, 2005 International Conference on Information and Communication Technology.

[15]  Brian Fitzgerald,et al.  Systems development methodologies: the problem of tenses , 2000, Inf. Technol. People.

[16]  D. Wegner,et al.  Transactive memory in close relationships. , 1991, Journal of personality and social psychology.

[17]  O. Murru,et al.  Assessing XP at a European Internet Company , 2003, IEEE Softw..

[18]  Joyce J. Elam,et al.  Inside a software design team: knowledge acquisition, sharing, and integration , 1993, CACM.

[19]  Keng Siau,et al.  Agile Modeling, Agile Software Development, and Extreme Programming: The State of Research , 2005, J. Database Manag..

[20]  Linda Rising,et al.  The Scrum Software Development Process for Small Teams , 2000, IEEE Softw..

[21]  John Byrne,et al.  Transactive memory system in new product development teams , 2006, IEEE Transactions on Engineering Management.

[22]  G. Johns.  The Essential Impact of Context on Organizational Behavior , 2006 .

[23]  Robert E. Kraut,et al.  Coordination in software development , 1995, CACM.

[24]  John W. Slocum,et al.  Technology, Structure, and Workgroup Effectiveness: A Test of a Contingency Model , 1984 .

[25]  Alistair Cockburn,et al.  Agile Software Development: The Business of Innovation , 2001, Computer.

[26]  Ronald F. Piccolo,et al.  A META‐ANALYSIS OF TEAMWORK PROCESSES: TESTS OF A MULTIDIMENSIONAL MODEL AND RELATIONSHIPS WITH TEAM EFFECTIVENESS CRITERIA , 2008 .

[27]  Weidong Xia,et al.  The ability of information systems development project teams to respond to business and technology changes: a study of flexibility measures , 2005, Eur. J. Inf. Syst..

[28]  Leslie A. Perlow,et al.  Contextualizing Patterns of Work Group Interaction: Toward a Nested Theory of Structuration , 2004, Organ. Sci..

[29]  Jane Wood,et al.  Joint Application Design: How to Design Quality Systems in 40% Less Time , 1989 .

[30]  James D. Thompson.  Organizations in Action , 1967 .

[31]  Larry E. Toothaker,et al.  Multiple Regression: Testing and Interpreting Interactions , 1991 .

[32]  L. Sproull,et al.  Coordinating Expertise in Software Development Teams , 2000 .

[33]  Audris Mockus,et al.  Shared Mental Models and Coordination in Large-Scale, Distributed Software Development , 2001, ICIS.

[34]  S. G. Cohen,et al.  What Makes Teams Work: Group Effectiveness Research from the Shop Floor to the Executive Suite , 1997 .

[35]  M. Iansiti,et al.  Developing products on Internet time. , 1997, Harvard business review.

[36]  Gordon B. Davis,et al.  Software Development Practices, Software Complexity, and Software Maintenance Performance: a Field Study , 1998 .

[37]  Bernhard Rumpe,et al.  Assumptions Underlying Agile Software-Development Processes , 2005, J. Database Manag..

[38]  Kent L. Beck,et al.  Embracing Change with Extreme Programming , 1999, Computer.

[39]  D. Hofmann,et al.  The Structure and Function of Collective Constructs: Implications for Multilevel Research and Theory Development , 1999 .

[40]  Venugopal Balijepally,et al.  Are Two Heads Better than One for Software Development? The Productivity Paradox of Pair Programming , 2009, MIS Q..

[41]  William L. Hays,et al.  Theory Testing in Organizational Behavior: The Varient Approach. , 1985 .

[42]  Robert C. Martin.  Agile Software Development, Principles, Patterns, and Practices , 2002 .

[43]  Jan Pries-Heje,et al.  Balancing Quality and Agility in Internet Speed Software Development , 2002, ICIS.

[44]  Dustin K. Jundt,et al.  Teams in organizations: from input-process-output models to IMOI models. , 2005, Annual review of psychology.

[45]  David F. Rico.  Effects of Agile Methods on Website Quality for Electronic Commerce , 2008, Proceedings of the 41st Annual Hawaii International Conference on System Sciences (HICSS 2008).

[46]  D. Wegner.  A Computer Network Model of Human Transactive Memory , 1995 .

[47]  Erran Carmel,et al.  PD and joint application design: a transatlantic comparison , 1993, CACM.

[48]  Ron Jeffries,et al.  Extreme Programming Installed , 2000 .

[49]  S. West,et al.  Multiple Regression: Testing and Interpreting Interactions. , 1994 .

[50]  JaatunMartin Gilje,et al.  Agile Software Development , 2002, Comput. Sci. Educ..

[51]  James Grenning,et al.  Launching Extreme Programming at a Process-Intensive Company , 2001, IEEE Softw..

[52]  Ray Reagans,et al.  Network Structure and Knowledge Transfer: The Effects of Cohesion and Range , 2003 .

[53]  Juhani Iivari,et al.  The Relationship Between Organisational Culture and the Deployment of Systems Development Methodologies , 2001, CAiSE.

[54]  John T. Nosek,et al.  The case for collaborative programming , 1998, CACM.

[55]  Michael A. Cusumano,et al.  Software Development Worldwide: The State of the Practice , 2003, IEEE Softw..

[56]  D. Chan.  Functional Relations among Constructs in the Same Content Domain at Different Levels of Analysis: A Typology of Composition Models , 1998 .

[57]  Keith C. C. Chan,et al.  Pair programming productivity: Novice-novice vs. expert-expert , 2006, Int. J. Hum. Comput. Stud..

[58]  Ramkrishnan V. Tenkasi,et al.  P ERSPECTIVE M AKING AND P ERSPECTIVE T AKING IN C OMMUNITIES OF K NOWING , 2000 .

[59]  Kyle Lewis.  Measuring transactive memory systems in the field: scale development and validation. , 2003, The Journal of applied psychology.

[60]  Robert F. DeVellis,et al.  Scale Development: Theory and Applications. , 1992 .

[61]  Andraž Cej,et al.  Agile software development with Scrum , 2010 .

[62]  D. Wegner.  Transactive Memory: A Contemporary Analysis of the Group Mind , 1987 .

[63]  Viswanath Venkatesh,et al.  A Control Theory Perspective on Agile Methodology Use and Changing User Requirements , 2009, Inf. Syst. Res..

[64]  S. Kozlowski,et al.  From Micro to Meso: Critical Steps in Conceptualizing and Conducting Multilevel Research , 2000 .

[65]  Suresh P. Sethi,et al.  Optimal Software Development: A Control Theoretic Approach , 2004, Inf. Syst. Res..

[66]  L. Argote.  Input uncertainty and organizational coordination in hospital emergency units. , 1982, Administrative science quarterly.

[67]  Brian Fitzgerald,et al.  Customising agile methods to software practices at Intel Shannon , 2006, Eur. J. Inf. Syst..

[68]  I. Nonaka,et al.  The Knowledge Creating Company , 2008 .

[69]  George Mangalaraj,et al.  Challenges of migrating to agile methodologies , 2005, CACM.

[70]  Younghwa Lee,et al.  Investigating factors affecting the adoption of anti-spyware systems , 2005, CACM.

[71]  Eliza Stefanova,et al.  Analyses of an agile methodology implementation , 2004, Proceedings. 30th Euromicro Conference, 2004..

[72]  Jan Chong,et al.  Social behaviors on XP and non-XP teams: a comparative study , 2005, Agile Development Conference (ADC'05).

[73]  Laurie A. Williams,et al.  All I really need to know about pair programming I learned in kindergarten , 2000, Commun. ACM.

[74]  Bill Curtis,et al.  A field study of the software design process for large systems , 1988, CACM.

[75]  K. Klein,et al.  Levels Issues in Theory Development, Data Collection, and Analysis , 1994 .

[76]  Chris F. Kemerer,et al.  Environmental Volatility, Development Decisions, and Software Volatility: A Longitudinal Analysis , 2006, Manag. Sci..

[77]  James T. Heires.  What I Did Last Summer: A Software Development Benchmarking Case Study , 2001, IEEE Softw..

[78]  Kent L. Beck,et al.  Test-driven Development - by example , 2002, The Addison-Wesley signature series.

[79]  Pär J. Ågerfalk,et al.  Agile Practices Reduce Distance in Global Software Development , 2006, Inf. Syst. Manag..

[80]  Laurie A. Williams,et al.  Experiments with Industry's “Pair-Programming” Model in the Computer Science Classroom , 2001, Comput. Sci. Educ..

[81]  P. Bliese.  Within-group agreement, non-independence, and reliability: Implications for data aggregation and analysis. , 2000 .

[82]  Pekka Abrahamsson,et al.  Extreme programming: a survey of empirical data from a controlled case study , 2004, Proceedings. 2004 International Symposium on Empirical Software Engineering, 2004. ISESE '04..

[83]  James D. Herbsleb,et al.  Team Knowledge and Coordination in Geographically Distributed Software Development , 2007, J. Manag. Inf. Syst..

[84]  Rudy Hirschheim,et al.  A Paradigmatic Analysis Contrasting Information Systems Development Approaches and Methodologies , 1998, Inf. Syst. Res..

[85]  Charles J. Poole,et al.  Using Extreme Programming in a Maintenance Environment , 2001, IEEE Softw..

[86]  Barry W. Boehm,et al.  Management challenges to implementing agile processes in traditional development organizations , 2005, IEEE Software.

[87]  Tore Dybå,et al.  Empirical studies of agile software development: A systematic review , 2008, Inf. Softw. Technol..

[88]  K. Beck,et al.  Extreme Programming Explained , 2002 .

[89]  Hakan Erdogmus,et al.  The Economics of Software Development by Pair Programmers , 2003 .

[90]  James M. Bieman.  Editorial: Risks to Software Quality , 2004, Software Quality Journal.

[91]  Dana E. Sims,et al.  Is there a “Big Five” in Teamwork? , 2005 .

[92]  Peter Schuh.  Recovery, Redemption, and Extreme Programming , 2001, IEEE Softw..

[93]  Scott B. MacKenzie,et al.  Common method biases in behavioral research: a critical review of the literature and recommended remedies. , 2003, The Journal of applied psychology.

[94]  Peter A. Bloniarz,et al.  A cost and performance model for Web service investment , 2000, CACM.

[95]  Deborah G. . Ancona,et al.  Bridging the Boundary: External Activity and Performance in Organizational Teams. , 1992 .

[96]  Xiaofeng Wang,et al.  Agile Practices in Use from an Innovation Assimilation Perspective: A Multiple Case Study , 2007, ICIS.

[97]  John E. Mathieu,et al.  A Temporally Based Framework and Taxonomy of Team Processes , 2001 .