Stakeholder Perceptions of the Adoption of Continuous Integration -- A Case Study

E. Laukkanen, M. Paasivaara, Teemu Arvonen
{"title":"Stakeholder Perceptions of the Adoption of Continuous Integration -- A Case Study","authors":"E. Laukkanen, M. Paasivaara, Teemu Arvonen","doi":"10.1109/Agile.2015.15","DOIUrl":null,"url":null,"abstract":"Continuous integration is an important support mechanism for fast delivery of new features. However, its adoption in industry has often been problematic, partly due to social challenges. However, there is little knowledge of the exact nature of the challenges, and how different stakeholders perceive the need for and adoption of continuous integration. In this paper, we describe how the introduction of continuous integration was perceived by different stakeholders in a R&D program at Ericsson. The case provided a rare opportunity to study the adoption of continuous integration in a large distributed organization. We interviewed 27 stakeholders and found differing perceptions of continuous integration: how suitable it is for the organization, how adoption should be organized, and whether it is possible to achieve sufficient quality through automated testing. These differences of perception were mainly consequences of the geographic distribution. Based on the case study, we propose three guidelines. First, understand that the product architecture has a significant effect on the adoption. However, do not let architectural problems keep you from implementing continuous integration. Second, give the team members sufficient time to overcome the initial learning phase in the adoption. Third, avoid centralizing competencies to individual sites, and invest in cross-site communication.","PeriodicalId":249378,"journal":{"name":"2015 Agile Conference","volume":"93-94 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2015-08-03","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"37","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2015 Agile Conference","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/Agile.2015.15","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 37

Abstract

Continuous integration is an important support mechanism for fast delivery of new features. However, its adoption in industry has often been problematic, partly due to social challenges. However, there is little knowledge of the exact nature of the challenges, and how different stakeholders perceive the need for and adoption of continuous integration. In this paper, we describe how the introduction of continuous integration was perceived by different stakeholders in a R&D program at Ericsson. The case provided a rare opportunity to study the adoption of continuous integration in a large distributed organization. We interviewed 27 stakeholders and found differing perceptions of continuous integration: how suitable it is for the organization, how adoption should be organized, and whether it is possible to achieve sufficient quality through automated testing. These differences of perception were mainly consequences of the geographic distribution. Based on the case study, we propose three guidelines. First, understand that the product architecture has a significant effect on the adoption. However, do not let architectural problems keep you from implementing continuous integration. Second, give the team members sufficient time to overcome the initial learning phase in the adoption. Third, avoid centralizing competencies to individual sites, and invest in cross-site communication.
利益相关者对采用持续集成的看法——一个案例研究
持续集成是快速交付新特性的重要支持机制。然而,它在工业中的应用往往存在问题,部分原因是社会挑战。然而,对于这些挑战的确切性质,以及不同的涉众如何看待持续集成的需要和采用,知之甚少。在本文中,我们描述了在爱立信的一个研发项目中,不同的利益相关者是如何感知持续集成的引入的。这个案例为研究在大型分布式组织中采用持续集成提供了难得的机会。我们采访了27个涉众,并发现了对持续集成的不同看法:它对组织有多适合,应该如何组织采用,以及是否有可能通过自动化测试达到足够的质量。这些认知差异主要是地理分布的结果。在案例分析的基础上,我们提出了三条指导原则。首先,要理解产品架构对采用有重要影响。但是,不要让架构问题阻碍您实现持续集成。其次,给团队成员足够的时间来克服采用过程中的初始学习阶段。第三,避免将能力集中到单个站点,并投资于跨站点的通信。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约1分钟内获得全文 求助全文
来源期刊
自引率
0.00%
发文量
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
copy
已复制链接
快去分享给好友吧!
我知道了
右上角分享
点击右上角分享
0
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:481959085
Book学术官方微信