Functional Size Measurement in Agile Development: Velocity in Agile Sprints

Proceedings of the 27th International Conference on Evaluation and Assessment in Software Engineering Pub Date : 2023-06-14 DOI:10.1145/3593434.3593486

Thomas Fehlmann, Andrea Gelli

{"title":"Functional Size Measurement in Agile Development: Velocity in Agile Sprints","authors":"Thomas Fehlmann, Andrea Gelli","doi":"10.1145/3593434.3593486","DOIUrl":null,"url":null,"abstract":"Agile teams measure their velocity for performance, based on Story Points. However, such velocity does not allow predicting when the product will be finished. Story points measure effort only. They do not discriminate between creating functionality and other tasks. Non-functional requirements (NFR), such as enhancing product quality, test coverage, removing technical debt, as well as process-related NFR such as agreeing with stakeholders, getting requirements right, or documenting, consume effort but do not add functionality. Thus, it remains unclear whether the product makes any progress, or the team is just looping around. Euro Project Office has therefore developed a method how to complement a product backlog by functional size, indicating progress and completeness in unambiguous terms. The method is based on the international standard ISO/IEC 14143 and ISO/IEC 19761. NFR are understood as in . Tools are available as open source and can be used by development teams with minimum investment into training.","PeriodicalId":178596,"journal":{"name":"Proceedings of the 27th International Conference on Evaluation and Assessment in Software Engineering","volume":"1 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2023-06-14","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings of the 27th International Conference on Evaluation and Assessment in Software Engineering","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/3593434.3593486","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}

引用次数: 0

Abstract

Agile teams measure their velocity for performance, based on Story Points. However, such velocity does not allow predicting when the product will be finished. Story points measure effort only. They do not discriminate between creating functionality and other tasks. Non-functional requirements (NFR), such as enhancing product quality, test coverage, removing technical debt, as well as process-related NFR such as agreeing with stakeholders, getting requirements right, or documenting, consume effort but do not add functionality. Thus, it remains unclear whether the product makes any progress, or the team is just looping around. Euro Project Office has therefore developed a method how to complement a product backlog by functional size, indicating progress and completeness in unambiguous terms. The method is based on the international standard ISO/IEC 14143 and ISO/IEC 19761. NFR are understood as in . Tools are available as open source and can be used by development teams with minimum investment into training.

查看原文本刊更多论文

敏捷开发中的功能规模度量:敏捷sprint中的速度

敏捷团队基于故事点来衡量他们的性能速度。然而，这样的速度无法预测产品何时完成。故事点只度量工作。它们不区分创建功能和其他任务。非功能性需求(NFR)，例如增强产品质量、测试覆盖率、消除技术债务，以及与过程相关的NFR，例如与涉众达成一致、获得正确的需求或文档化，消耗了工作，但不增加功能。因此，目前还不清楚产品是否取得了任何进展，或者团队只是在原地打转。因此，Euro Project Office开发了一种方法，如何通过功能大小来补充产品待办事项列表，以明确的方式指示进度和完成情况。该方法基于国际标准ISO/IEC 14143和ISO/IEC 19761。NFR可以理解为。这些工具是开源的，开发团队可以用最少的培训投资来使用它们。

本文章由计算机程序翻译，如有差异，请以英文原文为准。

求助全文

约1分钟内获得全文求助全文

来源期刊

Proceedings of the 27th International Conference on Evaluation and Assessment in Software Engineering

自引率

0.00%

发文量