A field study of the software design process for large systems
Communications of the ACM
Organizational obstacles to interface design and development: two participant-observer studies
ACM Transactions on Computer-Human Interaction (TOCHI)
Global software teams: collaborating across borders and time zones
Global software teams: collaborating across borders and time zones
Guest Editors' Introduction: Global Software Development
IEEE Software
Communication and Trust in Global Virtual Teams
Organization Science
It's About Time: Temporal Structuring in Organizations
Organization Science
The software engineering impacts of cultural factors on multi-cultural software development teams
Proceedings of the 25th International Conference on Software Engineering
HICSS '03 Proceedings of the 36th Annual Hawaii International Conference on System Sciences (HICSS'03) - Track1 - Volume 1
Culture Surprises in Remote Software Development Teams
Queue - Distributed Development
Usability and Internationalization of Information Technology (Volume in the Human Factors/Ergonomics Series)
In-group/out-group effects in distributed teams: an experimental simulation
CSCW '04 Proceedings of the 2004 ACM conference on Computer supported cooperative work
Hi-index | 0.02 |
Interaction between two teams with the same team leader and with similar size and goals moved from weekly face-to-face meetings to virtual meetings because of the temporary displacement of the team leader to a time zone six hours ahead of the rest of the team. One team focused primarily on software development and the second team on developing and testing a research instrument. The Software Team floundered through multiple different meeting arrangements and eventually agreed to disperse until the leader returned to the same time zone. In contrast, the Research Instrument Team kept a single meeting time that was set before it moved to virtual gatherings, and continued to be an active and productive team. This paper explores what factors led to this divergence in team success and concludes that the implicit temporal structures entraining the members of the Software Team coupled with an inability to repair member unhappiness and an unequal dispersion of skill sets among virtual and co-located members led to one team's eventual shutdown.