Method of Recommending a Scrum Team Composition for Intermediate Estimation of Software Development Projects

Teslyuk, Vasyl; Batyuk, Anatoliy; Voityshyn, Volodymyr

doi:10.1109/csit56902.2022.10000432

Cited by 2 publications

(10 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Although their definitiveness is higher, intermediate estimates are still not reliable enough to be used for commitments. Further information about intermediate estimation can be found in [9,10].…”

Section: Concept Of Estimation Life Cyclementioning

confidence: 99%

“…One of the core concepts of the authors' estimation framework [9,10] is the structure of software developer working time. The project working time (PWT), W, means total working time spent by a software engineer working on a project.…”

Section: Structure Of Software Developer Working Timementioning

confidence: 99%

“…The main outputs of the preliminary estimation are project scope (represented as an estimable-item breakdown structure, defined below), team composition, and project duration. Obviously, due to the quite high level of uncertainty, these outcomes are not supposed to be used for making commitments; instead, they will be elaborated on in the following stages: the intermediate and precise estimations [9,10].…”

Section: Introductionmentioning

confidence: 99%

“…The method of preliminary estimation proposed in this study is based on a simplified version of a system of working-time balance equations [9,10]. This applied simplification (in comparison with the intermediate estimation) aims, first of all, at the minimization of efforts spent on the estimation, intentionally sacrificing its accuracy.…”

Section: Introductionmentioning

confidence: 99%

“…The current study is a logical continuation of the authors' past works-the preliminary estimation method is based on their estimation framework [9,10]. This section is devoted to the basic terms and concepts introduced previously, in particular, the concept of the estimation life cycle, the structure of software developer working time, and the "normalization" approach to measure development efforts.…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

Preliminary Estimation for Software Development Projects Empowered with a Method of Recommending Optimal Duration and Team Composition

Teslyuk,

Batyuk,

Voityshyn

2024

ASI

Self Cite

View full text Add to dashboard Cite

In the early software development stages, the aim of estimation is to obtain a rough understanding of the timeline and resources required to implement a potential project. The current study is devoted to a method of preliminary estimation applicable at the beginning of the software development life cycle when the level of uncertainty is high. The authors’ concepts of the estimation life cycle, the estimable items breakdown structure, and a system of working-time balance equations in conjunction with an agile-fashioned sizing approach are used. To minimize the experts’ working time spent on preliminary estimation, the authors applied a decision support procedure based on integer programming and the analytic hierarchy process. The method’s outcomes are not definitive enough to make commitments; instead, they are supposed to be used for communication with project stakeholders or as inputs for the subsequent estimation stages. For practical usage of the preliminary estimation method, a semistructured business process is proposed.

show abstract

Section: Concept Of Estimation Life Cyclementioning

confidence: 99%

Section: Structure Of Software Developer Working Timementioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations