An Empirical Study of Speed and Communication in Globally Distributed Software Development

By James D. Herbsleb, Audris Mockus. IEEE Trans. Software Eng., 2003

1,087 citations recorded by the source corpus.

Subfields: Computer Science Applications, Information Systems

View Paper: https://www.semanticscholar.org/paper/9c8273273bfd3ac05f0a3e6c44728e2aabe49db7

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Computer Science Applications

In Information Systems

Citations in the corpus

Research Directions in Requirements Engineering (2007, background): “In particular, because geographic distance reduces team communication [85], ill-defined requirements are at risk of ultimately being misinterpreted, resulting in a system that does not meet the stakeholders’ needs.”
Familiarity, Complexity, and Team Performance in Geographically Distributed Software Development (2007, methodology): “Such data sources are often used in studies involving software teams ( Herbsleb and Mockus 2003, Kemerer and Slaughter 1999, Mockus and Herbsleb 2002).”
The impact of agile practices on communication in software development (2008, background): “Formal communication refers to explicit communication such as the specification documents (Herbsleb and Mockus 2003), and the status review meetings in software development (Kraut and Streeter 1995).”
The Impact of Ideology on Effectiveness in Open Source Software Development Teams (2006, methodology): “Studies of software development in distributed contexts (Herbsleb and Mockus 2003 ) and analyses of OSS projects such as Apache and Mozilla (Mockus et al. 2002) have used responses to modification requests as indicators of work accomplishment.”
Socio-technical congruence: a framework for assessing the impact of technical and work dependencies on software development productivity (2008, methodology): “Failure to discover the changes in coordination needs might have a profound impact on the quality of the product [15], on productivity [28] and even on the projects’ overall design [4].”
Global Software Development Challenges: A Case Study on Temporal, Geographical and Socio-Cultural Distance (2006, background): “Our study also reveals some of the solutions used by the companies to deal with these challenges.”
Team Knowledge and Coordination in Geographically Distributed Software Development (2007, background): “Adopting the right mix of coordination mechanisms can make software teams more productive [4], which is critical in competitive markets [40].”
Studying Software Engineers: Data Collection Techniques for Software Field Studies (2005, methodology): “Herbsleb and Mockus (2003) used data generated by a change management system to better understand how communication occurs in globally distributed software development.”
Offshoring and the global distribution of work: Implications for task interdependence theory and practice (2009, background): “Global distances cause breakdowns in face-to-face interactions and mutual adjustment processes that previously sustained collocated coordination processes (Herbsleb & Mockus, 2003).”
Global Software Engineering: The Future of Socio-technical Coordination (2007, background): “than co-located work [39], and suffers from a wide range of problems (see, e.”
Identification of coordination requirements: implications for the Design of collaboration and awareness tools (2006, methodology): “Those gaps could have major implications for the productivity and the quality of the output of product development organizations [7, 10, 16, 28] and for non-routine intellectual work more generally.”