The DOI matches its Crossref record; 7 of the 8 references it cites were found in a registry or an index.
Transitioning from a co-located to a globally-distributed software development team: a case study at Analog Devices Inc
Abstract
Global software development has become an extremely important issue for organizations at present in the climate of increasing tendency towards globalization and global outsourcing. A number of studies have been conducted which have identified a set of problematic-areas which are common across projects, including language and cultural differences, trust factors, communication across temporal and spatial distances, lack of shared contextual awareness. This study of global software development at Analog Devices Inc. (ADI) is especially noteworthy for a number of reasons. Firstly, the project has recently moved from a co-located to a globally-distributed one, and thus the team had already had experience of being co-located a factor that has not typically been the case in the studies published to date where teams are being established who have not previously been co-located. Also, as language and cultural factors were not an issue, the study was able to focus on the problems of communication over temporal and spatial distances. The study discusses how ADI attempted to address these problems and identifies the initiatives that worked well, and, more importantly, those that did not work as well. Among the findings was the fact that trust, which had been very solidly established among team members during co-location, was significantly eroded as the project team was reconstituted on a distributed basis.
Overview
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
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?
In the citing paper
“In addition to these issues, temporally dispersed collaborations are often plagued by delays, while co-located collaborations are considered more efficient [19].”
From Challenges and barriers in virtual teams: a literature review (2020) · cites this paper as [19]
In the citing paper
“Delays in responses from collaborators can be especially frustrating and problematic [116] and can lengthen the amount of time required to resolve issues [19], sometimes dragging problems out across multiple days [120,132].”
From Challenges and barriers in virtual teams: a literature review (2020) · cites this paper as [19]
In the citing paper
“Finally, developers starting their workday may become overwhelmed by the number of asynchronous messages left during the previous night [19].”
From Challenges and barriers in virtual teams: a literature review (2020) · cites this paper as [19]
In the citing paper
“and can leave the recipient feeling overwhelmed by the number of asynchronous messages left during the previous night [19].”
From Challenges and barriers in virtual teams: a literature review (2020) · cites this paper as [19]
Citations
Cites
Tactical approaches for alleviating distance in global software development
Carmel, E., & Agarwal, R. (2001) · IEEE Software · doi:10.1109/52.914734 · Cited by 708
Splitting the organization and integrating the code: Conway's law revisited
Herbsleb, J. D., & Grinter, R. E. (1999) · Proceedings of the 21st international conference on Software engineering · doi:10.1145/302405.302455 · Cited by 425
Distance, dependencies, and delay in a global collaboration
Herbsleb, J. D., Mockus, A., Finholt, T. A., & Grinter, R. E. (2000) · Proceedings of the 2000 ACM conference on Computer supported cooperative work · doi:10.1145/358916.359003 · Cited by 395
Leveraging resources in global software development
Battin, R. D., Crocker, R., Kreidler, J., & Subramanian, K. (2001) · IEEE Software · doi:10.1109/52.914750 · Cited by 274
Challenges of global software development
Mockus, A., & Herbsleb, J. D. (2002) · IEEE International Software Metrics Symposium (METRICS) · doi:10.1109/metric.2001.915526 · Cited by 123
(2003) · Cited by 60
Awareness meets requirements management: Awareness needs in Global Software Development
Damian, D., Chisan, J., Allen, P., & Corrie, B. (2003) · Cited by 37
Cited by
Challenges and barriers in virtual teams: a literature review
Morrison-Smith, S., & Ruiz, J. (2020) · SN Applied Sciences · doi:10.1007/s42452-020-2801-5 · Cited by 633
“, email, fax [19, 57]) allow collaborators to coordinate shared efforts across time and distance with the additional benefits of leaving a written communication history [31] that supports accountability and traceability [2].”
BackgroundInfluentialScaling agile methods to regulated environments: An industry case study
Fitzgerald, B. F., Stol, K.-J., O'Sullivan, R., & O’Brien, D. (2013) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1109/icse.2013.6606635 · Cited by 172
Distributed Agile Development: Using Scrum in a Large Project
Paasivaara, M., Durasiewicz, S., & Lassenius, C. (2008) · IEEE International Conference on Global Software Engineering (ICGSE) · doi:10.1109/icgse.2008.38 · Cited by 133
Scaling agile methods to regulated environments: an industry case study
Fitzgerald, B. F., Stol, K.-J., O'Sullivan, R., & O’Brien, D. (2013) · University of Limerick Institutional Repository (University of Limerick) · doi:10.5555/2486788.2486906 · Cited by 124
Benefits of Global Software Development: The Known and Unknown
Ågerfalk, P. J., Fitzgerald, B. F., Olsson, H. H., & Conchúir, E. Ó. (2008) · Springer eBooks · doi:10.1007/978-3-540-79588-9_1 · Cited by 109
“1 Formal Record of Communication Since asynchronous communication relies on technologies such as e-mail and fax [28, 29], a written communication history is usually left [7, 30].”
Background
Metadata
- Authors
- Boland, D.
- Corresponding author
- Boland, D.
- Venue
- "Third International Workshop on Global Software Development (GSD 2004)" W12S Workshop - 26th International Conference on Software Engineering
- Publisher
- IEE
- Published
- 2004
- Volume
- 2004
- Pages
- 4-7
- OpenAlex
- W2320223309
- Semantic Scholar
- 847f42e9198bcde71c2b68ab4c293f7b0b1b27d3
- Cited by
- 50
- References
- 8
- Citations by year
- 2025: 1 · 2024: 2 · 2023: 1 · 2021: 2 · 2020: 1 · 2017: 3 · 2016: 2 · 2015: 3 · 2014: 2 · 2013: 4 · 2012: 2
- FWCI
- 2.46
- Type
- conference paper
- Language
- en
- Open access
- closed
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Social Sciences › Psychology › Social Psychology › Team Dynamics and Performance
- Social Sciences › Business, Management and Accounting › Management Information Systems › Outsourcing and Supply Chain Management
- Keywords
- distributed software development, co-located teams, trust erosion, intercultural communication, language barriers, context awareness
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
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.
