Performance Criteria in Inter-Organizational Global Software Development Projects

Clear and well aligned performance criteria are fundamentally important in global software development projects. We found significant diversity in performance criteria between different projects done by a single company. The performance criteria were clear and aligned in simpler projects, whereas there was a lot of ambiguity in performance criteria in complex projects. The clarity of the performance criteria seems to have a positive effect on the project performance. Meeting the end-user needs was identified as a key performance criterion, and was often not properly covered in the project requirements or in explicit performance criteria. Long term view to project performance and management of expectations between the teams has an effect to project performance. Our research is based on a study of 18 inter-organizational software development projects in Nokia Corporation during 2006.

[1]  H. Keith Edwards,et al.  Analysis of the effectiveness of global virtual teams in software engineering projects , 2003, 36th Annual Hawaii International Conference on System Sciences, 2003. Proceedings of the.

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

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

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

[5]  J. Herbsleb,et al.  Global software development , 2001 .

[6]  Ilze Zigurs,et al.  Knowledge management in virtual projects: a research agenda , 2000, Proceedings of the 33rd Annual Hawaii International Conference on System Sciences.

[7]  Roger Atkinson,et al.  Project management: cost, time and quality, two best guesses and a phenomenon, its time to accept other success criteria , 1999 .

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

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

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

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

[12]  Casper Lassenius,et al.  Collaboration practices in global inter-organizational software development projects , 2003, Softw. Process. Improv. Pract..

[13]  Urvashi Rathod,et al.  Defining ‘success’ for software projects: An exploratory revelation , 2006 .

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

[15]  Maria Paasivaara,et al.  Communication practices in inter-organisational product development , 2005 .

[16]  James D. Herbsleb,et al.  Architectures, coordination, and distance: Conway’s law and beyond , 1999 .

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

[18]  Wanda J. Orlikowski,et al.  Knowing in practice: Enacting a collective capability in distributed organizing , 2002, STUDI ORGANIZZATIVI.

[19]  Julia Kotlarsky,et al.  Management of Globally Distributed Component-Based Software Development Projects , 2005 .

[20]  Manuel Castells,et al.  The Internet Galaxy: Reflections on the Internet, Business, and Society , 2001 .