How are Hybrid Development Approaches Organized? - A Systematic Literature Review

Nils Prenner, Carolin Unger-Windeler, K. Schneider
{"title":"How are Hybrid Development Approaches Organized? - A Systematic Literature Review","authors":"Nils Prenner, Carolin Unger-Windeler, K. Schneider","doi":"10.1145/3379177.3388907","DOIUrl":null,"url":null,"abstract":"Agile software development methods promise shorter time-to-market and higher product quality, but lack the ability of long-term planning or coping with large projects. However, software companies often also want the ability of long-term planning, promised by traditional or plan-based methods. To benefit from the strengths of both approaches, software companies often use a combination of agile and plan-based methods, known as hybrid development approaches. These approaches strongly depend on the individual context and are customized. Therefore, companies have to organize their hybrid development approach individually. However, practitioners often have difficulties with the organization of hybrid approaches. The organization considers how the phases, activities, roles, and artifacts are arranged and connected. Research lacks the necessary detailed insight into how hybrid development approaches are organized to support practitioners. To gain better understanding of the organization of hybrid approaches, we conducted a systematic literature review to gather descriptions of hybrid approaches. We analyzed the found papers thoroughly and could identify three general patterns of how hybrid approaches are organized. We found that all these patterns are still based on Royce’s waterfall model and use the standard software engineering activities. Our findings shall help to lead further research and help practitioners to better organize their individual development approach.","PeriodicalId":299473,"journal":{"name":"2020 IEEE/ACM International Conference on Software and System Processes (ICSSP)","volume":"86 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2020-06-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"14","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2020 IEEE/ACM International Conference on Software and System Processes (ICSSP)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/3379177.3388907","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 14

Abstract

Agile software development methods promise shorter time-to-market and higher product quality, but lack the ability of long-term planning or coping with large projects. However, software companies often also want the ability of long-term planning, promised by traditional or plan-based methods. To benefit from the strengths of both approaches, software companies often use a combination of agile and plan-based methods, known as hybrid development approaches. These approaches strongly depend on the individual context and are customized. Therefore, companies have to organize their hybrid development approach individually. However, practitioners often have difficulties with the organization of hybrid approaches. The organization considers how the phases, activities, roles, and artifacts are arranged and connected. Research lacks the necessary detailed insight into how hybrid development approaches are organized to support practitioners. To gain better understanding of the organization of hybrid approaches, we conducted a systematic literature review to gather descriptions of hybrid approaches. We analyzed the found papers thoroughly and could identify three general patterns of how hybrid approaches are organized. We found that all these patterns are still based on Royce’s waterfall model and use the standard software engineering activities. Our findings shall help to lead further research and help practitioners to better organize their individual development approach.
查看原文
分享 分享
微信好友 朋友圈 QQ好友 复制链接
本刊更多论文
混合开发方法是如何组织的?-系统文献综述
敏捷软件开发方法承诺更短的上市时间和更高的产品质量,但缺乏长期计划或应对大型项目的能力。然而,软件公司通常也希望有长期规划的能力,这是传统或基于计划的方法所承诺的。为了从这两种方法的优势中获益,软件公司经常使用敏捷和基于计划的方法的组合,称为混合开发方法。这些方法在很大程度上依赖于单个上下文,并且是定制的。因此,公司必须单独组织他们的混合开发方法。然而,从业者在组织混合方法时经常遇到困难。组织考虑如何安排和连接阶段、活动、角色和工件。对于如何组织混合开发方法来支持实践者,研究缺乏必要的详细见解。为了更好地理解混合方法的组织,我们进行了系统的文献综述,以收集混合方法的描述。我们对发现的论文进行了彻底的分析,并可以确定混合方法如何组织的三种一般模式。我们发现所有这些模式仍然基于Royce的瀑布模型,并使用标准的软件工程活动。我们的发现将有助于引导进一步的研究,并帮助从业者更好地组织他们的个人发展方法。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约1分钟内获得全文 去求助
来源期刊
自引率
0.00%
发文量
0
期刊最新文献
EcoKnow: Engineering Effective, Co-created and Compliant Adaptive Case Management Systems for Knowledge Workers Digital Re-imagination of Software and Systems Processes for Quality Engineering: iSPIN Approach Developing ML/DL Models: A Design Framework How are Hybrid Development Approaches Organized? - A Systematic Literature Review Constructing a Hybrid Software Process Simulation Model in Practice: An Exemplar from Industry
×
引用
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