Coping with distance: An empirical study of communication on the Jazz platform

Global software development - which is characterized by teams separated by physical distance and/or time-zone differences - has traditionally posed significant communication challenges. Often these have caused delays in completing tasks, or created misalignment across sites leading to re-work. In re...

Full description

Saved in:
Bibliographic Details
Main Authors: SINDHGATTA, Renuka, SENGUPTA, Bikram, DATTA, Subhajit
Format: text
Language:English
Published: Institutional Knowledge at Singapore Management University 2011
Subjects:
Online Access:https://ink.library.smu.edu.sg/sis_research/5574
https://ink.library.smu.edu.sg/context/sis_research/article/6577/viewcontent/Coping_with_distance_pv.pdf
Tags: Add Tag
No Tags, Be the first to tag this record!
Institution: Singapore Management University
Language: English
Description
Summary:Global software development - which is characterized by teams separated by physical distance and/or time-zone differences - has traditionally posed significant communication challenges. Often these have caused delays in completing tasks, or created misalignment across sites leading to re-work. In recent years, however, a new breed of development environments with rich collaboration features have emerged to facilitate cross-site work in distributed projects. In this paper we revisit the question "does distance matter?" in the context of IBM Jazz Platform -- a state-of-the-art collaborative development environment. We study the ecosystem of a large distributed team of around 300 members across 35 physical locations, which uses the Jazz platform for agile development. Our results indicate that while there is a delay in communication due to geographic separation, teams try to reduce the impact of delays by having a large percentage of work distributed within same/few time zones and working beyond regular office hours to interact with distributed teams. We observe different communication patterns depending on the roles of the team members, with component leads and project managers having a significantly higher overhead than development team members. We discuss the practical implications of our findings in terms of some best practices that can help lessen the impact of distance.