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].”
BackgroundPhilips experiences in global distributed software development
Kommeren, R., & Parviainen, P. (2007) · Empirical Software Engineering · doi:10.1007/s10664-007-9047-3 · Cited by 100
“On the other hand, several studies have indicated problems in distributed development, including Damian et al. 2004; Boland and Fitzgerald 2004; VA Software 2005): – Poor visibility and control of remote activities, – Inadequate communication, collaboration and coordination across individuals,…”
BackgroundPlease Turn Your Cameras on: Remote Onboarding of Software Developers During a Pandemic
Rodeghero, P., Zimmermann, T., Houck, B., & Ford, D. (2021) · IEEE/ACM International Conference on Software Engineering: Software Engineering in Practice (ICSE-SEIP) · doi:10.1109/icse-seip52600.2021.00013 · Cited by 119
Following the sun: Case studies in global software development
Treinen, J. J., & Miller-Frost, S. L. (2006) · IBM Systems Journal · doi:10.1147/sj.454.0773 · Cited by 101
Korkala, M., & Maurer, F. (2014) · Journal of Systems and Software · doi:10.1016/j.jss.2014.03.080 · Cited by 76
Pirkkalainen, H., & Pawlowski, J. Μ. (2013) · Computers in Human Behavior · doi:10.1016/j.chb.2013.07.041 · Cited by 84
A reference model for successful Distributed Development of Software Systems
Lings, B., Lundell, B., Ågerfalk, P. J., & Fitzgerald, B. F. (2007) · IEEE International Conference on Global Software Engineering (ICGSE) · doi:10.1109/icgse.2007.6 · Cited by 56
Developing Trust In Virtual Software Development Teams
Casey, V. (2010) · Journal of theoretical and applied electronic commerce research · doi:10.4067/s0718-18762010000200004 · Cited by 48
“In these circumstances it is relevant to note that the development of trust in a virtual team can be a difficult and complex endeavor [4].”
BackgroundResultBenefits of global software development: exploring the unexplored
Conchúir, E. Ó., Olsson, H. H., Ågerfalk, P. J., & Fitzgerald, B. F. (2009) · Software Process Improvement and Practice · doi:10.1002/spip.417 · Cited by 49
A review of awareness in distributed collaborative software engineering
Omoronyia, I., Ferguson, J., Roper, M., & Wood, M. (2010) · Software Practice and Experience · doi:10.1002/spe.1005 · Cited by 39
Using Developer Activity Data to Enhance Awareness during Collaborative Software Development
Omoronyia, I., Ferguson, J., Roper, M., & Wood, M. (2009) · Computer Supported Cooperative Work (CSCW) · doi:10.1007/s10606-009-9104-0 · Cited by 37
“They include poor visibility and control of remote resources; inadequate communication, collaboration and coordination across distributed teams; diminishing trust; and lack of shared contextual awareness (Boland and Fitzgerald 2004; Chisan and Damian 2004; Hargreaves and Damian 2004).”
BackgroundA framework for supporting management in distributed information systems development
Ralyté, J., Lamielle, X., Arni-Bloch, N., & Léonard, M. (2008) · International Conference on Research Challenges in Information Science (RCIS) · doi:10.1109/rcis.2008.4632128 · Cited by 20
Ten Strategies for Successful Distributed Development
Lings, B., Lundell, B., Ågerfalk, P. J., & Fitzgerald, B. F. (2006) · Kluwer Academic Publishers eBooks · doi:10.1007/0-387-34410-1_9 · Cited by 20
“Boland and Fitzgerald (2004) report on the use of quarterly sync-up meetings as a very successful strategy for maintaining morale and motivation among team members.”
InfluentialHargreaves, E., Damian, D., Lanubile, F., & Chisan, J. (2004) · ACM SIGSOFT Software Engineering Notes · doi:10.1145/1022494.1022502 · Cited by 15
“In Transitioning from a Co-located to a Globally-Distributed Software Development Team: A Case Study at Analog Devices, Inc, Boland discusses from a first-hand perspective the impact of transferring previously collocated team members from the United States to Ireland and the negative impact that this relocation had on…”
BackgroundOutsourcing software development the remote project manager's perspective
Casey, V., Deshpande, S., & Richardson, I. (2010) · Arrow@dit (Dublin Institute of Technology) · doi:10.34961/9521 · Cited by 13
Technological support for distributed agile development
Dullemond, K., & van Gameren, B. (2009) · Research Repository (Delft University of Technology) · Cited by 12
A Cognitive Perspective for Choosing Groupware Tools and Elicitation Techniques in Virtual Teams
Aranda, G. N., Vizcaíno, A., Cechich, A., & Piattini, M. G. (2005) · Lecture notes in computer science · doi:10.1007/11424758_111 · Cited by 11
Distributed Information Systems Development: A Framework for Understanding & Managing.
Ralyté, J., Lamielle, X., Arni-Bloch, N., & Léonard, M. (2008) · International journal of computer science and applications · Cited by 12
The 3rd international workshop on global software development
Damian, D., & Lanubile, F. (2004) · doi:10.5555/998675.999503 · Cited by 11
Can FOSS projects benefit from integrating Kanban: a case study
Harzl, A. (2017) · Journal of Internet Services and Applications · doi:10.1186/s13174-017-0058-z · Cited by 14
“A large body of research has been published on agile methods [12] and their adoption in distributed settings [5, 30] since the publication of the agile manifesto.”
BackgroundExploring The Missing Link Between Trust in Business Negotiation and Virtual Work
Santos, M., & Dias, M. D. O. (2024) · European Journal of Theoretical and Applied Sciences · doi:10.59324/ejtas.2024.2(2).26 · Cited by 7
Evaluating the Quality of Proposed Agile XScrum Model
Qureshi, M. R. J. (2017) · International Journal of Modern Education and Computer Science · doi:10.5815/ijmecs.2017.11.05 · Cited by 7
“Although XP has enormous strengths but still significant number of software companies are hesitant to transfer from plan driven methodologies to XP [8].”
BackgroundZhang, S., Zhang, T., Cheng, J., & Zhou, S. (2025) · Proceedings of the ACM on Human-Computer Interaction · doi:10.1145/3711105 · Cited by 16
“Researchers have explored collaboration practices and challenges among SDEs in diverse contexts, including co-located environments [7, 14, 105], distributed environments [43, 50, 80], as well as the transition [16, 64] and comparison [25, 56] between the two scenarios.”
ABB Experiences of Boosting Controlling and Monitoring Activities in Collaborative Production
Tihinen, M., Parviainen, P., Suomalainen, T., Karhu, K., & Mannevaara, M. (2011) · IEEE International Conference on Global Software Engineering (ICGSE) · doi:10.1109/icgse.2011.12 · Cited by 6
“The meetings are organized mostly as face to face meetings, however, some project managers need to attend the meeting also remotely, i.e. virtual meeting practices are required.”
BackgroundGlobal software development: a multiple-case study of the realisation of the benefits
Conchúir, E. Ó. (2010) · University of Limerick Institutional Repository (University of Limerick) · Cited by 5
Optimal Team Composition in Distributed Software Development
van Cann, R. (2012) · Palgrave Macmillan UK eBooks · doi:10.1057/9780230362994_11 · Cited by 4
Why Should I Trust in a Virtual Community Member?
Soto, J. P., Vizcaíno, A., Portillo-Rodríguez, J., & Piattini, M. G. (2009) · Lecture notes in computer science · doi:10.1007/978-3-642-04216-4_10 · Cited by 4
“Other problems in this kind of environment are related to communication and coordination, and are made more difficult as a result of differences in culture, timetable, language, etc [6].”
BackgroundThe Seven Forces That Shape Trust in Virtual Negotiation: A Qualitative Study
Santos, M., & Dias, M. D. O. (2024) · Open Journal of Business and Management · doi:10.4236/ojbm.2024.124113 · Cited by 30
“Another issue is that synchronous (call, video call) or asynchronous (e-mail, text messaging) communication are challenging factors in this work model (Boland & Fitzgerald, 2004; Damian & Zowghi, 2002; O’Leary et al., 2012).”
Combining FOSS and Kanban: An Action Research
Harzl, A. (2016) · IFIP advances in information and communication technology · doi:10.1007/978-3-319-39225-7_6 · Cited by 3
“Since the publication of the agile manifesto in 2001 a large body of research has been published on agile methods [9], e.g. on adopting agile methods [4] and implementing agile methods in distributed settings [5, 22].”
MethodØverland, L. H. (2006) · NORA - Norwegian Open Research Archives · Cited by 3
Vornanen, M. (2017) · Tampere University Institutional Repository (Tampere University) · Cited by 3
Khoshroo, B. M., & Rashidi, H. (2009) · exhibition · doi:10.1109/ieeegcc.2009.5734307 · Cited by 2
“- trust issues (CC) - language differences (CC) - informal communication (CC) - delays (CC) - isolation (CC) - lack of shared context (Aw) - different organizational culture (Aw) - expertise identification and selection (Aw) [2,4,5,7,12,16,18,27] [1,2,4,5,11,12,16,27] [1,3,8,5,12-14,16-19] [3,4,13,16,17,25] [27] [3,4,…”
InfluentialLessons in global software development – local to global transition within a regulated environment
Cawley, O., & Richardson, I. (2010) · University of Limerick Institutional Repository (University of Limerick) · doi:10.34961/9479 · Cited by 2
Leveraging Crowdsourcing in Cloud Application Development
Aldhahari, E., Abuhussein, A., & Shiva, S. G. (2015) · doi:10.2316/p.2015.829-019 · Cited by 2
Recomendações para a Gerência de Projetos no Desenvolvimento Distribuído de Software
Siqueira, F. L., & Silva, P. S. M. (2006) · Simpósio Brasileiro de Qualidade de Software (SBQS) · doi:10.5753/sbqs.2006.15599 · Cited by 2
“…a dificuldade de obtenção de vistos para viagens de negócio [21], a falta de horários comuns de trabalho [20], as diferenças de suporte técnico e de vendas de uma ferramenta em diferentes países [3], a falta de confiança entre as pessoas [4], a demora na resolução de problemas [20], entre outros.”
BackgroundHuman Sustainability in Software Development
Ramautar, V., Overbeek, S. J., & España, S. (2021) · Springer eBooks · doi:10.1007/978-3-030-69970-3_14 · Cited by 2
Using global pairs for reducing software development time
Jalote, P., & Gupta, A. K. (2011) · India Software Engineering Conference · doi:10.1145/1953355.1953372 · Cited by 2
“[ 4 , 10]). Another body of work has focused on tools and techniques to alleviate some of the problems that come up in GSD (e.g.”
BackgroundCustomer communication in distributed agile software development
Korkala, M. (2015) · Cited by 1
Measurement-based management of global software development projects
Tihinen, M. (2014) · Cited by 1
An Open Source Approach to Improving GIS Implementations in Developing Countries
Øverland, J. H. (2010) · NORA - Norwegian Open Research Archives · Cited by 1
Challenges When Using Scrum in Globally Distributed Teams
Shah, S. (2016)
Teambeziehungen stärken – vom Miteinander zum Füreinander
Pannier, N. (2023) · Haufe eBooks · doi:10.34157/978-3-648-16790-8_7
Rangevik, A. (2013) · KTH Publication Database DiVA (KTH Royal Institute of Technology)
Communicating Architectural Design Rules Using Models – An Action Case Study
Mattsson, A., Lundell, B., & Fitzgerald, B. F. (2012) · Informing Science and IT Education Conference · doi:10.28945/1669
A framework for considering opportunities and threats in distributed software development
Agerfalk, P. J., Fitzgerald, B., Holmstrom Olsson, H., Lings, B., Lundell, B., & Ó Conchúir, E. (2005) · Austrian Computer Society · doi:10.34961/437 · Cited by 190
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.
