Towards Improving the Organization of Hybrid Development Approaches

Nils Prenner
{"title":"Towards Improving the Organization of Hybrid Development Approaches","authors":"Nils Prenner","doi":"10.1145/3379177.3390304","DOIUrl":null,"url":null,"abstract":"Agile methods were proposed to address the problems of traditional or plan-based software development, e.g., late customer feedback or resistance to change. However, unlike plan-based methods, they are not designed for long-term planning or to cope with large projects. Software companies want the ability of a fast reaction to changes but also the ability of long-term planning. To profit from the strength of both approaches, software companies often use a combination of agile and plan-based methods, called hybrid development approaches. These approaches depend on the respective context of each company. Therefore, the companies have to properly arrange and connect the phases, activities, roles, and artifacts from plan-based and agile approaches individually in their hybrid development approach. This is considered as the organization of hybrid development approaches. However, the organization of hybrid approaches is often difficult for the companies. Until now, research considers only the chosen development methods without the organization of hybrid development approaches. With my work, I want to strengthen the understanding of how hybrid approaches are organized and get a detailed picture of the challenges when organizing hybrid approaches. Based on my findings, I want to develop measures to support practitioners while organizing their development approach.","PeriodicalId":299473,"journal":{"name":"2020 IEEE/ACM International Conference on Software and System Processes (ICSSP)","volume":"84 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2020-06-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"5","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.3390304","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 5

Abstract

Agile methods were proposed to address the problems of traditional or plan-based software development, e.g., late customer feedback or resistance to change. However, unlike plan-based methods, they are not designed for long-term planning or to cope with large projects. Software companies want the ability of a fast reaction to changes but also the ability of long-term planning. To profit from the strength of both approaches, software companies often use a combination of agile and plan-based methods, called hybrid development approaches. These approaches depend on the respective context of each company. Therefore, the companies have to properly arrange and connect the phases, activities, roles, and artifacts from plan-based and agile approaches individually in their hybrid development approach. This is considered as the organization of hybrid development approaches. However, the organization of hybrid approaches is often difficult for the companies. Until now, research considers only the chosen development methods without the organization of hybrid development approaches. With my work, I want to strengthen the understanding of how hybrid approaches are organized and get a detailed picture of the challenges when organizing hybrid approaches. Based on my findings, I want to develop measures to support practitioners while organizing their development approach.
查看原文
分享 分享
微信好友 朋友圈 QQ好友 复制链接
本刊更多论文
改进混合开发方法的组织
敏捷方法的提出是为了解决传统的或基于计划的软件开发的问题,例如,延迟客户反馈或抗拒更改。然而,与基于计划的方法不同,它们不是为长期规划或应对大型项目而设计的。软件公司既需要对变化做出快速反应的能力,也需要长期规划的能力。为了从这两种方法的优势中获利,软件公司经常使用敏捷和基于计划的方法的组合,称为混合开发方法。这些方法取决于每个公司各自的环境。因此,公司必须在混合开发方法中适当地安排和连接基于计划的方法和敏捷方法中的阶段、活动、角色和工件。这被认为是混合开发方法的组织。然而,混合方法的组织对公司来说往往是困难的。到目前为止,研究只考虑所选择的开发方法,而没有组织混合开发方法。通过我的工作,我希望加强对如何组织混合方法的理解,并详细了解组织混合方法时面临的挑战。基于我的发现,我想开发一些方法来支持实践者组织他们的开发方法。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约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