{"title":"A novel method to early agile effort estimation through functional initiatives","authors":"Wilson Rosa, Sara Jardine","doi":"10.1016/j.jss.2024.112302","DOIUrl":null,"url":null,"abstract":"<div><h3>Context</h3><div>Decision makers struggle to develop rough order of magnitude cost estimates early in an agile software project's lifecycle, when lack of detailed functional user requirements limits Functional Size Measurement.</div></div><div><h3>Objective</h3><div>This study introduces a new method based on counting initiatives to measure the functional size (Functional Initiative Count (FIC) and Functional Initiative Points (FIP) of agile software projects during their early phases and examines its effectiveness as a predictor of agile software development effort. FIC and FIP are derived from an agile project's high-level initiatives converted into similar size units based on their active verbs. Initiatives, also referred to as <em>capabilities</em> in the Department of Homeland Security (DHS) and Department of Defense (DoD), identifies the means to accomplish a mission, function, or objective. Initiatives are typically documented early in a project's product vision document, product roadmap document, or concept of operations (in the DHS and DoD).</div></div><div><h3>Method</h3><div>The analysis used historical actual data from 21 agile projects implemented between 2014 and 2022 in the DHS and DoD.</div></div><div><h3>Result</h3><div>FIC revealed to be a reliable predictor of total software development effort, while FIP revealed to be an even better predictor of total software development effort.</div></div><div><h3>Conclusion</h3><div>Using FIP is a viable solution to use as a functional size measure for early phase agile software development effort estimation.</div></div>","PeriodicalId":51099,"journal":{"name":"Journal of Systems and Software","volume":"223 ","pages":"Article 112302"},"PeriodicalIF":3.7000,"publicationDate":"2024-11-28","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Journal of Systems and Software","FirstCategoryId":"94","ListUrlMain":"https://www.sciencedirect.com/science/article/pii/S0164121224003467","RegionNum":2,"RegionCategory":"计算机科学","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"Q1","JCRName":"COMPUTER SCIENCE, SOFTWARE ENGINEERING","Score":null,"Total":0}
引用次数: 0
Abstract
Context
Decision makers struggle to develop rough order of magnitude cost estimates early in an agile software project's lifecycle, when lack of detailed functional user requirements limits Functional Size Measurement.
Objective
This study introduces a new method based on counting initiatives to measure the functional size (Functional Initiative Count (FIC) and Functional Initiative Points (FIP) of agile software projects during their early phases and examines its effectiveness as a predictor of agile software development effort. FIC and FIP are derived from an agile project's high-level initiatives converted into similar size units based on their active verbs. Initiatives, also referred to as capabilities in the Department of Homeland Security (DHS) and Department of Defense (DoD), identifies the means to accomplish a mission, function, or objective. Initiatives are typically documented early in a project's product vision document, product roadmap document, or concept of operations (in the DHS and DoD).
Method
The analysis used historical actual data from 21 agile projects implemented between 2014 and 2022 in the DHS and DoD.
Result
FIC revealed to be a reliable predictor of total software development effort, while FIP revealed to be an even better predictor of total software development effort.
Conclusion
Using FIP is a viable solution to use as a functional size measure for early phase agile software development effort estimation.
期刊介绍:
The Journal of Systems and Software publishes papers covering all aspects of software engineering and related hardware-software-systems issues. All articles should include a validation of the idea presented, e.g. through case studies, experiments, or systematic comparisons with other approaches already in practice. Topics of interest include, but are not limited to:
•Methods and tools for, and empirical studies on, software requirements, design, architecture, verification and validation, maintenance and evolution
•Agile, model-driven, service-oriented, open source and global software development
•Approaches for mobile, multiprocessing, real-time, distributed, cloud-based, dependable and virtualized systems
•Human factors and management concerns of software development
•Data management and big data issues of software systems
•Metrics and evaluation, data mining of software development resources
•Business and economic aspects of software development processes
The journal welcomes state-of-the-art surveys and reports of practical experience for all of these topics.