A Comparison of Industrial Process Descriptions for Global Custom Software Development

Global Software Development (GSD) is associated with many potential pitfalls. Some of these pitfalls, such as the lack of a structured and agreed upon process and unclear tasks, roles and responsibilities can be alleviated by using a process description. While GSD takes up a large percentage of industrial software development, it remains unclear whether organizations tailor their process descriptions for GSD-specific issues. This paper reports results of a comparative study of GSD process descriptions used for custom software development of three industrial organizations. The two methods applied in this research are in-depth analysis of process descriptions and interviews with process designers. We conclude that the level of detail of the process descriptions varies strongly and that the intended use of the prescribed process does not necessarily correspond with the provided level of detail. Also, the design of the process descriptions seems to be partly dependent on the expertise and professional background of the process designers. Other important factors in the design and intended use of the process descriptions are the size of an organization and organizational maturity.

[1]  Steven Hall,et al.  Managing Global Development Risk , 2007 .

[2]  P. Krutchen,et al.  The Rational Unified Process: An Introduction , 2000 .

[3]  Rafael Prikladnicki,et al.  A Reference Model for Global Software Development: Findings from a Case Study , 2006, 2006 IEEE International Conference on Global Software Engineering (ICGSE'06).

[4]  Siegfried Zopf Success factors for globally distributed projects , 2009 .

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

[6]  Frederik D. Wiersema,et al.  Customer intimacy and other value disciplines , 1993 .

[7]  Audris Mockus,et al.  Globalization by Chunking: A Quantitative Approach , 2001, IEEE Softw..

[8]  Kevin C. Desouza,et al.  Managing knowledge in distributed projects , 2004, CACM.

[9]  Mario Piattini,et al.  Challenges and Improvements in Distributed Software Development: A Systematic Review , 2009, Adv. Softw. Eng..

[10]  Audris Mockus,et al.  Challenges of global software development , 2001, Proceedings Seventh International Software Metrics Symposium.

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

[12]  Christof Ebert,et al.  Point Counterpoint , 2012, IEEE Software.

[13]  Tony Gorschek,et al.  Empirical evidence in global software engineering: a systematic review , 2010, Empirical Software Engineering.

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

[15]  Michael A. Cusumano Managing software development in globally distributed teams , 2008, CACM.

[16]  Frank Salger On the Use of Handover Checkpoints to Manage the Global Software Development Process , 2009, OTM Workshops.

[17]  Rebecca E. Grinter Doing Software Development: Occasions for Automation and Formalisation , 1997, ECSCW.