The scale and evolution of coordination needs in large-scale distributed projects: implications for the future generation of collaborative tools

The past decade has witnessed the development of a new class of coordination tools that focus on automatically providing individuals a rich context for facilitating the coordination of their work. Despite their valuable contributions, current coordination tools have mostly been designed without taking into account scalability aspects beyond the small-group level. The increasing pervasiveness of large-scale projects suggests that those mechanisms need to scale dramatically to adequately support such work settings. In this paper, we used data from five distinct large-scale projects from three different companies to study the scale, range, and volatility of the coordination requirements that emerged over time within those projects. Our results showed that coordination requirements tend to be quite volatile, vary significantly in their magnitude across project members and a significant proportion of the coordination requirements cut across organizational and geographical boundaries. Furthermore, new coordination requirements represent, on average, a third of the coordination requirements faced by a project member on a monthly basis. The implications of these results for the design of collaborative tools are discussed.

[1]  Randall Frost,et al.  Jazz and the Eclipse Way of Collaboration , 2007, IEEE Software.

[2]  Christian Heath,et al.  Collaboration and controlCrisis management and multimedia technology in London Underground Line Control Rooms , 1992, Computer Supported Cooperative Work (CSCW).

[3]  Saul Greenberg,et al.  TeamRooms: network places for collaboration , 1996, CSCW '96.

[4]  David F. Redmiles,et al.  The Awareness Network, To Whom Should I Display My Actions? And, Whose Actions Should I Monitor? , 2011, IEEE Transactions on Software Engineering.

[5]  Paul Dourish,et al.  "Breaking the code", moving between private and public work in collaborative software development , 2003, GROUP.

[6]  Daniela E. Damian,et al.  Does Socio-Technical Congruence Have an Effect on Software Build Success? A Study of Coordination in a Software Project , 2011, IEEE Transactions on Software Engineering.

[7]  Ivan Herman,et al.  Graph Visualization and Navigation in Information Visualization: A Survey , 2000, IEEE Trans. Vis. Comput. Graph..

[8]  Daniel M. Germán,et al.  What do large commits tell us?: a taxonomical study of large commits , 2008, MSR '08.

[9]  Anita Sarma,et al.  Tesseract: Interactive visual exploration of socio-technical relationships in software development , 2009, 2009 IEEE 31st International Conference on Software Engineering.

[10]  Geraldine Fitzpatrick,et al.  CVS integration with notification and chat: lightweight software team collaboration , 2006, CSCW '06.

[11]  Christoph Treude,et al.  Awareness 2.0: staying aware of projects, developers and tasks using dashboards and feeds , 2010, 2010 ACM/IEEE 32nd International Conference on Software Engineering.

[12]  Jonathon N. Cummings,et al.  The Spatial, Temporal, and Configurational Characteristics of Geographic Dispersion in Teams , 2007, MIS Q..

[13]  Carl Gutwin,et al.  Group awareness in distributed software development , 2004, CSCW.

[14]  Paul Dourish,et al.  Portholes: supporting awareness in a distributed work group , 1992, CHI.

[15]  Geraldine Fitzpatrick,et al.  Augmenting the workaday world with Elvin , 1999, ECSCW.

[16]  Gail C. Murphy,et al.  Recommending Emergent Teams , 2007, Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007).

[17]  André van der Hoek,et al.  Palantir: raising awareness among configuration management workspaces , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[18]  James D. Herbsleb,et al.  Coordination Breakdowns and Their Impact on Development Productivity and Software Failures , 2013, IEEE Transactions on Software Engineering.

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

[20]  Li-Te Cheng,et al.  Jazzing up Eclipse with collaborative tools , 2003, eclipse '03.

[21]  J. Alberto Espinosa,et al.  Crossing Spatial and Temporal Boundaries in Globally Distributed Projects: A Relational Model of Coordination Delay , 2009, Inf. Syst. Res..

[22]  James D. Herbsleb,et al.  Identification of coordination requirements: implications for the Design of collaboration and awareness tools , 2006, CSCW '06.

[23]  James D. Herbsleb,et al.  Socio-technical congruence: a framework for assessing the impact of technical and work dependencies on software development productivity , 2008, ESEM '08.

[24]  Robert E. Kraut,et al.  Patterns of contact and communication in scientific research collaboration , 1990, CSCW '88.

[25]  James D. Herbsleb,et al.  COMMUNICATION, TEAM PERFORMANCE, AND THE INDIVIDUAL: BRIDGING TECHNICAL DEPENDENCIES. , 2010 .

[26]  Sirkka L. Jarvenpaa,et al.  Communication and Trust in Global Virtual Teams , 1999, J. Comput. Mediat. Commun..

[27]  Paul Dourish,et al.  Awareness and coordination in shared workspaces , 1992, CSCW '92.

[28]  Kjeld Schmidt,et al.  The Problem with `Awareness': Introductory Remarks on `Awareness in CSCW' , 2002, Computer Supported Cooperative Work (CSCW).

[29]  David F. Redmiles,et al.  Bridging the gap between technical and social dependencies with Ariadne , 2005, eclipse '05.

[30]  Lucas Layman,et al.  Coordination in large-scale software teams , 2009, 2009 ICSE Workshop on Cooperative and Human Aspects on Software Engineering.

[31]  André van der Hoek,et al.  Empirical evidence of the benefits of workspace awareness in software configuration management , 2008, SIGSOFT '08/FSE-16.

[32]  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).