对在敏捷软件开发项目中使用“完成定义”的系统回顾

Ana Silva, Thalles Araújo, João Nunes, M. Perkusich, E. Dilorenzo, H. Almeida, A. Perkusich
{"title":"对在敏捷软件开发项目中使用“完成定义”的系统回顾","authors":"Ana Silva, Thalles Araújo, João Nunes, M. Perkusich, E. Dilorenzo, H. Almeida, A. Perkusich","doi":"10.1145/3084226.3084262","DOIUrl":null,"url":null,"abstract":"Background: Definition of Done (DoD) is a Scrum practice that consists of a simple list of criteria that adds verifiable or demonstrable value to the product. It is one of the most popular agile practices and assures a balance between short-term delivery of features and long-term product quality, but little is known of its actual use in Agile teams. Objective: To identify possible gaps in the literature and define a starting point to define DoD for practitioners through the identification and synthesis of the DoD criteria used in agile projects as presented in the scientific literature. Method: We applied a Systematic Literature Review of studies published up to (and including) 2016 through database search and backward and forward snowballing. Results: In total, we evaluated 2326 papers, of which 8 included DoD criteria used in agile projects. We identified that some studies presented up to 4 levels of DoD, which include story, sprint, release or project. We identified 62 done criteria, which are related to software verification and validation, deploy, code inspection, test process quality, regulatory compliance, software architecture design, process management, configuration management and non-functional requirements. Conclusion: The main implication for research is a need for more and better empirical studies documenting and evaluating the use of the DoD in agile software development. For the industry, the review provides a map of how DoD is currently being used in the industry and can be used as a starting point to define or compare with their own DoD definition.","PeriodicalId":192290,"journal":{"name":"Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering","volume":"6 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2017-06-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"27","resultStr":"{\"title\":\"A systematic review on the use of Definition of Done on agile software development projects\",\"authors\":\"Ana Silva, Thalles Araújo, João Nunes, M. Perkusich, E. Dilorenzo, H. Almeida, A. Perkusich\",\"doi\":\"10.1145/3084226.3084262\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Background: Definition of Done (DoD) is a Scrum practice that consists of a simple list of criteria that adds verifiable or demonstrable value to the product. It is one of the most popular agile practices and assures a balance between short-term delivery of features and long-term product quality, but little is known of its actual use in Agile teams. Objective: To identify possible gaps in the literature and define a starting point to define DoD for practitioners through the identification and synthesis of the DoD criteria used in agile projects as presented in the scientific literature. Method: We applied a Systematic Literature Review of studies published up to (and including) 2016 through database search and backward and forward snowballing. Results: In total, we evaluated 2326 papers, of which 8 included DoD criteria used in agile projects. We identified that some studies presented up to 4 levels of DoD, which include story, sprint, release or project. We identified 62 done criteria, which are related to software verification and validation, deploy, code inspection, test process quality, regulatory compliance, software architecture design, process management, configuration management and non-functional requirements. Conclusion: The main implication for research is a need for more and better empirical studies documenting and evaluating the use of the DoD in agile software development. For the industry, the review provides a map of how DoD is currently being used in the industry and can be used as a starting point to define or compare with their own DoD definition.\",\"PeriodicalId\":192290,\"journal\":{\"name\":\"Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering\",\"volume\":\"6 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2017-06-15\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"27\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1145/3084226.3084262\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/3084226.3084262","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 27

摘要

背景:完成定义(DoD)是一种Scrum实践,它由一列简单的标准组成,这些标准为产品增加了可验证或可演示的价值。它是最流行的敏捷实践之一,确保了短期功能交付和长期产品质量之间的平衡,但它在敏捷团队中的实际应用却鲜为人知。目标:识别文献中可能存在的空白,并定义一个起点,通过识别和综合科学文献中敏捷项目中使用的DoD标准,为实践者定义DoD。方法:通过数据库检索和前后滚雪球法,对截至(包括)2016年发表的研究进行了系统文献综述。结果:我们总共评估了2326篇论文,其中8篇包含了敏捷项目中使用的DoD标准。我们发现一些研究提出了多达4个层次的DoD,包括故事、冲刺、发布或项目。我们确定了62个已完成的标准,它们与软件验证和确认、部署、代码检查、测试过程质量、法规遵从性、软件架构设计、过程管理、配置管理和非功能需求相关。结论:研究的主要含义是需要更多更好的实证研究来记录和评估敏捷软件开发中DoD的使用。对于行业而言,该审查提供了DoD目前在行业中如何使用的地图,可以用作定义或与他们自己的DoD定义进行比较的起点。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
A systematic review on the use of Definition of Done on agile software development projects
Background: Definition of Done (DoD) is a Scrum practice that consists of a simple list of criteria that adds verifiable or demonstrable value to the product. It is one of the most popular agile practices and assures a balance between short-term delivery of features and long-term product quality, but little is known of its actual use in Agile teams. Objective: To identify possible gaps in the literature and define a starting point to define DoD for practitioners through the identification and synthesis of the DoD criteria used in agile projects as presented in the scientific literature. Method: We applied a Systematic Literature Review of studies published up to (and including) 2016 through database search and backward and forward snowballing. Results: In total, we evaluated 2326 papers, of which 8 included DoD criteria used in agile projects. We identified that some studies presented up to 4 levels of DoD, which include story, sprint, release or project. We identified 62 done criteria, which are related to software verification and validation, deploy, code inspection, test process quality, regulatory compliance, software architecture design, process management, configuration management and non-functional requirements. Conclusion: The main implication for research is a need for more and better empirical studies documenting and evaluating the use of the DoD in agile software development. For the industry, the review provides a map of how DoD is currently being used in the industry and can be used as a starting point to define or compare with their own DoD definition.
求助全文
通过发布文献求助,成功后即可免费获取论文全文。 去求助
来源期刊
自引率
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学术文献互助群
群 号:604180095
Book学术官方微信