2021 IEEE/ACM 13th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE) 2021
DOI: 10.1109/chase52884.2021.00015
|View full text |Cite
|
Sign up to set email alerts
|

Buying time in software development: how estimates become commitments?

Abstract: Despite years of research for improving accuracy, software practitioners still face software estimation difficulties. Expert judgment has been the prevalent method used in industry, and researchers' focus on raising realism in estimates when using it seems not to be enough for the much-expected improvements. Instead of focusing on the estimation process's technicalities, we investigated the interaction of the establishment of commitments with customers and software estimation. By observing estimation sessions … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
3
0

Year Published

2022
2022
2024
2024

Publication Types

Select...
5
3

Relationship

1
7

Authors

Journals

citations
Cited by 10 publications
(3 citation statements)
references
References 37 publications
0
3
0
Order By: Relevance
“…The first was a systematic literature mapping of factors affecting software estimates when using expert-judgment [5]. The second was a qualitative study in industry, investigating how practitioners transform estimates into commitments [34]. These two studies evidenced the problem of pressure over estimates, leading practitioners to either change their estimates to more "acceptable" ones to stakeholders or to use padding of other tasks/projects to compensate for unrealistic commitments.…”
Section: A the Approach Designmentioning
confidence: 99%
“…The first was a systematic literature mapping of factors affecting software estimates when using expert-judgment [5]. The second was a qualitative study in industry, investigating how practitioners transform estimates into commitments [34]. These two studies evidenced the problem of pressure over estimates, leading practitioners to either change their estimates to more "acceptable" ones to stakeholders or to use padding of other tasks/projects to compensate for unrealistic commitments.…”
Section: A the Approach Designmentioning
confidence: 99%
“…Agile methodologies emerged to reduce the risk of not completing the development of large systems due to budget, technological or resource constraints, among other reasons [ 47 , 48 ]. The emergence of agile methodologies made it possible to improve the success rate of software development projects and reduce the budget consumption of projects that are finally abandoned [ 49 , 50 ].…”
Section: Introductionmentioning
confidence: 99%
“…Usually, receptors want to hit these targets. Previous research has shown that sometimes estimators are pressured to change their estimates [17] to meet targets when the software estimates collide with them [5], making estimates acceptable to receptors, or "defensible" [18]. In addition, time pressure-the perception that time is scarce considering the tasks' demands-is standard in the software industry, and commercial pressure is behind many of its causes [16].…”
Section: Introductionmentioning
confidence: 99%