Exploring the Assumed Benefits of Global Software Development

In existing global software development (GSD) literature, much focus has been on identifying the challenges that practitioners may face (such as socio-cultural and temporal distance issues), while potential benefits have not been extensively analyzed. We reverse this trend by studying these potential benefits. We question whether they are well-founded assumptions and whether they are attainable in practice. This paper presents findings from a multi-case study at three multi-national companies that have extensive experience in GSD. We identify the benefits mentioned in GSD literature, analyze them with regards to the companies' experiences and then conclude whether or not each benefit is being realized in practice. Our findings reveal that the realization of the assumed benefits cannot be simply taken for granted

[1]  Mary Lacity,et al.  Twenty Practices for Offshore Sourcing , 2004, MIS Q. Executive.

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

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

[4]  Daniela E. Damian,et al.  Addressing the challenges of software industry globalization: the workshop on global software development , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[5]  D. L. Parnas,et al.  On the criteria to be used in decomposing systems into modules , 1972, Software Pioneers.

[6]  Rebecca E. Grinter Decomposition : ABSTRACT Putting It All Back , 2022 .

[7]  François Bourguignon,et al.  Annual World Bank Conference on Development Economics 2004: Accelerating Development , 2004 .

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

[9]  A. Strauss,et al.  Basics of qualitative research: Grounded theory procedures and techniques. , 1992 .

[10]  A. Olsson,et al.  Addressing the challenge. , 1998, European heart journal.

[11]  Pär J. Ågerfalk,et al.  Global software development: never mind the problems – are there really any benefits? , 2006 .

[12]  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..

[13]  K. Sauvant Unctad's World Investment Report 2004: The Shift Towards Services , 2005 .

[14]  L. Kiel Experiences in Distributed Development: A Case Study , 2003 .

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

[16]  Pär J. Ågerfalk,et al.  A framework for considering opportunities and threats in distributed software development , 2005 .

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

[18]  James D. Herbsleb,et al.  Splitting the organization and integrating the code: Conway's law revisited , 1999, Proceedings of the 1999 International Conference on Software Engineering (IEEE Cat. No.99CB37002).

[19]  J. Alberto Espinosa,et al.  The effect of time separation on coordination costs in global software teams: a dyad model , 2004, 37th Annual Hawaii International Conference on System Sciences, 2004. Proceedings of the.

[20]  Erran Carmel,et al.  Global software teams: collaborating across borders and time zones , 1999 .

[21]  Daniela E. Damian,et al.  The impact of stakeholders' geographical distribution on managing requirements in a multi-site organization , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.

[22]  M. E. Conway HOW DO COMMITTEES INVENT , 1967 .

[23]  James D. Herbsleb,et al.  The geography of coordination: dealing with distance in R&D work , 1999, GROUP.

[24]  Pamela Jordan Basics of qualitative research: Grounded theory procedures and techniques , 1994 .

[25]  Audris Mockus,et al.  Distance, dependencies, and delay in a global collaboration , 2000, CSCW '00.