Cited by 420Team Dynamics and PerformanceSoftware Engineering Techniques and PracticesOpen Source Software Innovations

Familiarity, complexity, and team performance in geographically distributed software development

Espinosa, J. Alberto, Slaughter, Sandra A., Kraut, Robert E., Herbsleb, James D.·2007·Organization Science

Abstract

While prior research has found that familiarity is beneficial to team performance, it is not clear whether different kinds of familiarity are more or less beneficial when the work has different types of complexity. In this paper, we theorize how task and team familiarity interact with task and team coordination complexity to influence team performance. We posit that task familiarity is more beneficial with more complex tasks (i.e., tasks that are larger or with more complex structures) and that team familiarity is more beneficial when team coordination is more difficult (i.e., for larger or geographically dispersed teams). Finally, we propose that the effects of task familiarity and team familiarity on team performance are complementary. Based on a field study of geographically distributed software teams, two of our hypotheses are disconfirmed: Our results show that the beneficial effects of task familiarity decline when tasks are more structurally complex and are independent of task size. Conversely, the hypotheses for team familiarity are confirmed as the benefit of team familiarity for team performance is enhanced when team coordination is more challenging—i.e., when teams are larger or geographically dispersed. Finally, surprisingly, we find that task and team familiarity are more substitutive than complementary in their joint effects on team performance: Task familiarity improves team performance more strongly when team familiarity is weak and vice versa. Our study contr…

Integrity signals

Registry

Crossref · 10.1287/orsc.1070.0297

Cites

6 of 6 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

Cites

Flagged first, then by citations

Cited by

Sorted by citations

Authors
Espinosa, J. A., Slaughter, S. A., Kraut, R. E., & Herbsleb, J. D.
Affiliations
  • American University (US)
  • Georgia Institute of Technology (US)
  • Carnegie Mellon University (US)
Venue
Organization Science
Published
2007-08
Volume
18
Issue
4
Pages
613-630
ISSN
  • 1047-7039 (ISSN-L)
  • 1526-5455
OpenAlex
W2112389050
Cited by
420
References
6
Citations by year
2026: 14 · 2025: 20 · 2024: 17 · 2023: 17 · 2022: 27 · 2021: 25 · 2020: 27 · 2019: 16 · 2018: 28 · 2017: 27 · 2016: 23 · 2015: 23 · 2014: 38 · 2013: 24 · 2012: 23
FWCI
20.67
Type
journal article
Language
en
Open access
closed
Locations
Organization Science (publishedVersion)
Topics
  • Social Sciences › Psychology › Social Psychology › Team Dynamics and Performance
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Physical Sciences › Computer Science › Computer Science Applications › Open Source Software Innovations
Keywords
task familiarity, team familiarity, team performance, geographically dispersed teams, software development teams, task complexity, task size, structural complexity, team size

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review