Familiarity, Complexity, and Team Performance in Geographically Distributed Software Development.¶
Espinosa, J. A., Slaughter, S. A., Kraut, R. E., & Herbsleb, J. D. (2007). Familiarity, Complexity, and Team Performance in Geographically Distributed Software Development. Organization Science, 18(4), 613-630.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Hebbian Learning
- A team that rotates its incident-room assignments so every pair eventually coacts is running a Hebbian intervention, structurally identical to a cortex tuning its receptive fields to input statistics.
This sourceField study showing team familiarity built through repeated joint work improves coordination and team performance, especially as coordination becomes more challenging.
Supported in partVerified against the publisher's abstract
Supplies field evidence that team familiarity from repeated joint work pays off most when coordination is hard, but says nothing about Hebbian mechanisms or cortical receptive-field tuning.
“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.”
- A team that rotates its incident-room assignments so every pair eventually coacts is running a Hebbian intervention, structurally identical to a cortex tuning its receptive fields to input statistics.
Verification¶
Does it exist? Confirmed. This work's DOI resolves to a registered record, which fixes its identity. That is all it fixes.
Does it back the claim? Read against the text for 1 of 1 citation: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:4e66de235c02 · see in the full table