Towards Just-Enough Documentation for Agile Effort Estimation: What Information Should Be Documented?

Pasuksmit, Jirat; Thongtanunam, Patanamon; Karunasekera, Shanika

doi:10.1109/icsme52107.2021.00017

Cited by 8 publications

(2 citation statements)

References 41 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Both studies reported that the Agile practitioners may re-estimate the work item when the related information is changed. However, a recent survey study pointed out that practitioners would re-estimate a work item if the information change is significant (Pasuksmit et al 2021). Yet, it is still unclear what types of information change are associated with SP changes.…”

Section: Effort Estimationmentioning

confidence: 99%

Story points changes in agile iterative development

2022

Self Cite

View full text Add to dashboard Cite

Story Points (SP) are an effort unit that is used to represent the relative effort of a work item. In Agile software development, SP allows a development team to estimate their delivery capacity and facilitate the sprint planning activities. Although Agile embraces changes, SP changes after the sprint planning may negatively impact the sprint plan. To minimize the impact, there is a need to better understand the SP changes and an automated approach to predict the SP changes. Hence, to better understand the SP changes, we examine the prevalence, accuracy, and impact of information changes on SP changes. Through the analyses based on 19,349 work items spread across seven open-source projects, we find that on average, 10% of the work items have SP changes. These work items typically have SP value increased by 58%-100% relative to the initial SP value when they were assigned to a sprint. We also find that the unchanged SP reflect the development time better than the changed SP. Our qualitative analysis shows that the work items with changed SP often have the information changes relating to updating the scope of work. Our empirical results suggest that SP and the scope of work should be reviewed prior or during sprint planning to achieve a reliable sprint plan. Yet, it could be a tedious task to review all work items in the product (or sprint) backlog. Therefore, we develop a classifier to predict whether a work item will have SP changes after being assigned to a sprint. Our classifier achieves an AUC of 0.69-0.8, which is significantly better than the baselines. Our results suggest that to better manage and prepare for the unreliability in SP estimation, the team can leverage our insights and the classifier during the sprint planning. To facilitate future studies, we provide the replication package and the datasets, which are available online.

show abstract

Section: Effort Estimationmentioning

confidence: 99%

Story points changes in agile iterative development

2022

Self Cite

View full text Add to dashboard Cite

show abstract

“…Technology is represented by indicators of diversity and sophistication or novelty. Finally, coding is an indicator for developing a program, while the size and complexity indicators represent the database (Hamouda, 2014;Khatri et al, 2016;Pasuksmit et al, 2021;Rosa et al, 2021;Sommerville, 2011;Yuliansyah et al, 2018).…”

Section: Questionnairementioning

confidence: 99%

Significant Factors in Agile Software Development of Effort Estimation

Sudarmaningtyas¹,

Mohamed²

2022

JST

View full text Add to dashboard Cite

The Agile effort estimation involves project-related and people-related factors. This research objective is to find the factors that influence Agile effort estimation significantly through path analysis using a structural equation model. This research built an agile effort estimation path coefficient model from six constructs from theories and previous studies. Project-related factors represent by requirement and design implementation constructs. People-related factors are measured by the construct of experience, knowledge, and technical ability. The last construct is the effort itself. SmartPLS is employed for the confirmatory composite analysis and the structural model assessment. The confirmatory composite analysis indicated that all constructs are reliable and valid. Furthermore, the structural model assessment found that all factors of project-related constructs have a positive relationship and significant influence, showing a coefficient path value of 59.1% between requirement and design implementation constructs. All constructs represent people-related factors indicated by the coefficient path value of 67% between experience and knowledge, 42.6% between experience and technical ability, and 54.4% between knowledge and technical ability. In addition, all constructs proved influential simultaneously to effort by 31.1%. Positively contribute provided by requirement, experience, and technology’s ability. Significantly influenced provided by constructs of the developer’s knowledge and technical ability. The largest effect is given by technical ability, knowledge, and experience on medium and small scales. Contrarily, both constructs from project-related effects can be negligible because there was no influence. Based on the result, this study concludes that the significant factors in Agile effort estimation are technical ability, knowledge, and experience.

show abstract

Topology of the Documentation Landscape

Raglianti¹

2022

2022 IEEE/ACM 44th International Conference on Software Engineering: Companion Proceedings (ICSE-Companion)

View full text Add to dashboard Cite

Towards Just-Enough Documentation for Agile Effort Estimation: What Information Should Be Documented?

Cited by 8 publications

References 41 publications

Story points changes in agile iterative development

Story points changes in agile iterative development

Significant Factors in Agile Software Development of Effort Estimation

Topology of the Documentation Landscape

Contact Info

Product

Resources

About