Studying the impact of global software development characteristics on project goals: a causal model

Despite the growing importance of global software development (GSD), a high failure rate of GSD projects is reported in the literature. In order to understand the underlying reasons, the goals of GSD projects and the special charac- teristics of GSD that might have an influence on these goals have to be identified. This article presents a combined litera- ture and interview study aimed at identifying goals and influencing factors in GSD and integrates them into a causal model. The article presents the goal and design of the study; the literature review, which resulted in a preliminary model of factors and cause-effect relationships; and the revision of the model based on interviews with practitioners in GSD.

[1]  Christof Ebert,et al.  Surviving Global Software Development , 2001, IEEE Softw..

[2]  Sachidanandam Sakthivel,et al.  Managing risk in offshore systems development , 2007, CACM.

[3]  K. Subramanian,et al.  Leveraging Resources in Global Software Development , 2001, IEEE Softw..

[4]  Rafael Prikladnicki,et al.  Software configuration management over a global software development environment: lessons learned from a case study , 2006, GSD '06.

[5]  B. Wong,et al.  Relationship Issues in Global Software Development Enterprises , 2008 .

[6]  James J. Treinen,et al.  Following the sun: Case studies in global software development , 2006, IBM Syst. J..

[7]  R. Bhagat.  Culture's Consequences: Comparing Values, Behaviors, Institutions, and Organizations Across Nations , 2002 .

[8]  Rajesh Krishna Balan,et al.  Globally distributed software development project performance: an empirical analysis , 2008, ISEC '08.

[9]  J. Alberto Espinosa,et al.  Bridging Global Boundaries for IS Project Success , 2005, Proceedings of the 38th Annual Hawaii International Conference on System Sciences.

[10]  Philippe Kruchten,et al.  Cultural patterns in software process mishaps: incidents in global projects , 2005 .

[11]  Nils Brede Moe,et al.  Understanding a lack of trust in Global Software Teams: a multiple-case study , 2008, Softw. Process. Improv. Pract..

[12]  Brian Lings,et al.  Distributed development in an intra-national, intra-organisational context: an experience report , 2006, GSD '06.

[13]  Daniela E. Damian,et al.  Guest Editors' Introduction: Global Software Development: How Far Have We Come? , 2006, IEEE Software.

[14]  Seth Stovack Kessler.  Piezoelectric-based in-situ damage detection of composite materials for structural health monitoring systems , 2002 .

[15]  Jürgen Münch,et al.  A Decision Model for Supporting Task Allocation Processes in Global Software Development , 2009, PROFES.

[16]  Ellis Horowitz,et al.  Software Cost Estimation with COCOMO II , 2000 .

[17]  R. L. Feldmann,et al.  Outsourcing in India , 2001, IEEE Softw..

[18]  James D. Herbsleb,et al.  Guest Editors' Introduction: Global Software Development , 2001, IEEE Softw..

[19]  Marcelo Cataldo,et al.  Siemens Global Studio Project: Experiences Adopting an Integrated GSD Infrastructure , 2006, 2006 IEEE International Conference on Global Software Engineering (ICGSE'06).

[20]  Audris Mockus,et al.  An Empirical Study of Speed and Communication in Globally Distributed Software Development , 2003, IEEE Trans. Software Eng..

[21]  Darja Šmite,et al.  Understanding a lack of trust in Global Software Teams: a multiple-case study , 2008 .

[22]  Ita Richardson,et al.  Uncovering the reality within virtual software teams , 2006, GSD '06.

[23]  Erran Carmel,et al.  Tactical Approaches for Alleviating Distance in Global Software Development , 2001, IEEE Softw..

[24]  J.D. Herbsleb,et al.  Global software development at Siemens: experience from nine projects , 2005, Proceedings. 27th International Conference on Software Engineering, 2005. ICSE 2005..

[25]  Sanjaya Mishra,et al.  Research methods in the social sciences , 2005 .

[26]  J. Hart.  [Qualitative methods]. , 2000, Recherche en soins infirmiers.

[27]  Sjaak Brinkkemper,et al.  Reasons for Success and Failure in Offshore Software Development Projects , 2008, ECIS.

[28]  Päivi Parviainen,et al.  Philips experiences in global distributed software development , 2007, Empirical Software Engineering.

[29]  Pamela Abbott,et al.  Why 'nearshore' means that distance matters , 2007, CACM.

[30]  J. Alberto Espinosa,et al.  Do Gradations of Time Zone Separation Make a Difference in Performance? A First Laboratory Study , 2007, International Conference on Global Software Engineering (ICGSE 2007).

[31]  Nilay V. Oza,et al.  Difficulties in Managing Offshore Software Outsourcing Relationships: An Empirical Analysis of 18 High Maturity Indian Software Companies , 2005 .

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

[33]  Darja Smite.  Global Software Development Project Management - Distance Overcoming , 2004, EuroSPI.

[34]  Jürgen Münch,et al.  A Survey on the State of the Practice in Distributed Software Development: Criteria for Task Allocation , 2009, 2009 Fourth IEEE International Conference on Global Software Engineering.

[35]  E. Prater,et al.  A Research Framework for the Impact of Cultural Differences on IT Outsourcing , 2006 .

[36]  Seija Komi-Sirviö,et al.  Lessons learned by participants of distributed software development , 2005 .

[37]  Richard Heeks,et al.  Synching or Sinking: Global Software Outsourcing Relationships , 2001, IEEE Softw..

[38]  Philippe Kruchten,et al.  Cultural patterns in software process mishaps , 2005, ACM SIGSOFT Softw. Eng. Notes.

[39]  Jürgen Münch,et al.  TAMRI: A Tool for Supporting Task Distribution in Global Software Development Projects , 2009, 2009 Fourth IEEE International Conference on Global Software Engineering.

[40]  Daniel Paulish.  Global Software Development Process Research at Siemens , 2004 .