Communication Challenges and Strategies in Distributed DevOps
Abstract
Even though agile actively seeks collaboration from all its stakeholders, most agile projects do not extend themselves toward the operations people. To solve this problem, DevOps is introduced. DevOps is a conceptual framework for reintegrating development and operations of Information Systems, which is able to break the wall between developers and operations professionals. DevOps improves the work through a collection of principles and practices, centered around close collaboration between Development and Operations personnel. However, both sides have paid little attention to issues faced by each other. Communication gaps is a recurrent problem in agile teams that is also eminent in the relationship between developers and operations. Literature offers little research on this aspect of communication in DevOps. This position paper describes the communication practices from a distributed agile team composed of developers and operations based on communication challenges (geographical, socio-cultural, and temporal distance) and strategies (frequency, direction, modality, and content). From the results we outline possible research focus for future work, aiming to enrich the academia research on the matter as well as to help practitioners to improve their working practices.
Integrity signals
Registry
Cites
Statistics
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?
A communication issue arises as a result of the geographic separation between the testing and development groups.
“In [105], the authors noted that a communication issue arises as a result of the geographic separation between the testing and development groups.”
From Challenges and Solutions in Implementing Continuous Integration and Continuous Testing for Agile Quality Assurance (2023) · cites this paper as [105]
Cites
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 · see citing works
People, organizations, and process improvement
Perry, D. E., Staudenmayer, N. A., & Votta, L. G. (1994) · IEEE Software · doi:10.1109/52.300082 · Cited by 401 · see citing works
Flagged first, then by citations
Cited by
Sorted by citations
Identifying the primary dimensions of DevSecOps: A multi-vocal literature review
Zhao, X., Clear, T., & Lal, R. (2024) · Journal of Systems and Software · doi:10.1016/j.jss.2024.112063 · Cited by 40 · see citing works
Grande, R., Vizcaíno, A., & García, F. O. (2024) · Computer Standards & Interfaces · doi:10.1016/j.csi.2023.103767 · Cited by 30 · see citing works
Bhanushali, A. (2023) · International Journal of Science and Research (IJSR) · doi:10.21275/sr231021114758 · Cited by 11 · see citing works
- Authors
- Diel, E., Marczak, S., & Cruzes, D. S.
- Affiliations
- Pontifícia Universidade Católica do Rio Grande do Sul (BR)
- SINTEF (NO)
- Venue
- 2016 IEEE 11th International Conference on Global Software Engineering (ICGSE)
- Publisher
- IEEE
- Published
- 2016-08
- Pages
- 24-28
- OpenAlex
- W2525854532
- Cited by
- 51
- References
- 2
- Citations by year
- 2026: 2 · 2025: 2 · 2024: 7 · 2023: 11 · 2022: 12 · 2021: 4 · 2020: 6 · 2019: 4 · 2018: 2 · 2017: 1
- FWCI
- 1.98
- Type
- conference paper
- Language
- en
- Open access
- closed
- Locations
- IEEE International Conference on Global Software Engineering (ICGSE) (publishedVersion)
- Funders
- Norges Forskningsråd
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Social Sciences › Psychology › Social Psychology › Team Dynamics and Performance
- Physical Sciences › Computer Science › Computer Networks and Communications › Software System Performance and Reliability
- Keywords
- DevOps, communication difficulties, communication strategies, geographic distance, socio-cultural distance, temporal distance, communication modality, communication frequency
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