Platform Teams: An Organizational Structure for Continuous Delivery

Leonardo A. F. Leite, Fabio Kon, Gustavo Pinto, Paulo Meirelles
{"title":"Platform Teams: An Organizational Structure for Continuous Delivery","authors":"Leonardo A. F. Leite, Fabio Kon, Gustavo Pinto, Paulo Meirelles","doi":"10.1145/3387940.3391455","DOIUrl":null,"url":null,"abstract":"Software-producing organizations are seeking to release faster and more efficiently new versions of their products to their customers to remain competitive in the fierce software market. Continuous delivery practices arise as a potential solution since every commit to the repository could result in a production-candidate version of a product, accelerating time to market, and improving customer satisfaction. In this work, we employed Grounded Theory to investigate how organizations pursuing continuous delivery should organize their development and operations teams. We collected data from 27 IT professionals. After a careful analysis, we started the elaboration of a taxonomy with four patterns of organizational structures: (1) siloed departments, (2) classical DevOps, (3) cross-functional teams, and (4) platform teams. We observed that the platform team structure is the most distinctive classification of our taxonomy, and it has promising results regarding delivery performance. Some relevant aspects we found out about platform teams include: infrastructure specialists need coding skills; product teams have to operate their business services; and much of the non-functional concerns are handled by the platform, alleviating product teams.","PeriodicalId":309659,"journal":{"name":"Proceedings of the IEEE/ACM 42nd International Conference on Software Engineering Workshops","volume":null,"pages":null},"PeriodicalIF":0.0000,"publicationDate":"2020-06-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"10","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings of the IEEE/ACM 42nd International Conference on Software Engineering Workshops","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/3387940.3391455","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 10

Abstract

Software-producing organizations are seeking to release faster and more efficiently new versions of their products to their customers to remain competitive in the fierce software market. Continuous delivery practices arise as a potential solution since every commit to the repository could result in a production-candidate version of a product, accelerating time to market, and improving customer satisfaction. In this work, we employed Grounded Theory to investigate how organizations pursuing continuous delivery should organize their development and operations teams. We collected data from 27 IT professionals. After a careful analysis, we started the elaboration of a taxonomy with four patterns of organizational structures: (1) siloed departments, (2) classical DevOps, (3) cross-functional teams, and (4) platform teams. We observed that the platform team structure is the most distinctive classification of our taxonomy, and it has promising results regarding delivery performance. Some relevant aspects we found out about platform teams include: infrastructure specialists need coding skills; product teams have to operate their business services; and much of the non-functional concerns are handled by the platform, alleviating product teams.
查看原文
分享 分享
微信好友 朋友圈 QQ好友 复制链接
本刊更多论文
平台团队:持续交付的组织结构
软件生产组织正在寻求更快、更有效地向客户发布其产品的新版本,以便在激烈的软件市场中保持竞争力。持续交付实践作为一种潜在的解决方案出现,因为对存储库的每次提交都可能产生产品的生产候选版本,从而加快产品上市时间,并提高客户满意度。在这项工作中,我们使用扎根理论来调查追求持续交付的组织应该如何组织他们的开发和运营团队。我们收集了27位IT专业人士的数据。经过仔细的分析,我们开始细化一个包含四种组织结构模式的分类法:(1)竖井部门,(2)经典DevOps,(3)跨职能团队,(4)平台团队。我们观察到,平台团队结构是我们分类法中最独特的分类,它在交付性能方面有很好的结果。我们发现平台团队的一些相关方面包括:基础设施专家需要编码技能;产品团队必须运营他们的业务服务;而且很多非功能性的问题都由平台来处理,减轻了产品团队的负担。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约1分钟内获得全文 去求助
来源期刊
自引率
0.00%
发文量
0
期刊最新文献
A Preliminary Systematic Mapping on Software Engineering for Robotic Systems: A Software Quality Perspective Generating API Test Data Using Deep Reinforcement Learning Human Factors in the Study of Automatic Software Repair: Future Directions for Research with Industry Strategies for Crowdworkers to Overcome Barriers in Competition-based Software Crowdsourcing Development Centralized Generic Interfaces in Hardware/Software Co-design for AI Accelerators
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
现在去查看 取消
×
提示
确定
0
微信
客服QQ
Book学术公众号 扫码关注我们
反馈
×
意见反馈
请填写您的意见或建议
请填写您的手机或邮箱
已复制链接
已复制链接
快去分享给好友吧!
我知道了
×
扫码分享
扫码分享
Book学术官方微信
Book学术文献互助
Book学术文献互助群
群 号:481959085
Book学术
文献互助 智能选刊 最新文献 互助须知 联系我们:info@booksci.cn
Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。
Copyright © 2023 Book学术 All rights reserved.
ghs 京公网安备 11010802042870号 京ICP备2023020795号-1