Impacts of agile requirements documentation debt on software projects: A retrospective study. Mendes, T., De Farias, M., Mendonça, M., Soares, H., Kalinowski, M., & Spínola, R. 2016. cited By
Impacts of agile requirements documentation debt on software projects: A retrospective study [link]Paper  doi  abstract   bibtex   
Documentation debt is a type of technical debt that describes problems in documentation such as missing, inadequate or incomplete artifacts. Unlike traditional methods, agile methodologies usually employ short iterative cycles and rely on tacit knowledge within a team. In particular, Agile Requirements (AR) (e.g., user stories) tend to reduce the focus on requirements specification activities. This scenario contributes to the occurrence of documentation debt. The goal of this paper is to investigate the impact that this type of debt brings to projects developed by using AR. We address this goal by performing a retrospective study in a real software project that used AR in its development. Our analysis was concentrated on data from 132 maintenance and evolution tasks. Of this total, 65 were related to the presence of documentation debt and were performed within a timeframe of 18 months. The findings indicated an extra maintenance effort of about 47% of the total effort estimated for developing the project and an extra cost of about 48% of the initial cost of the development phase. © 2016 ACM.
@CONFERENCE{Mendes20161290,
author={Mendes, T.S. and De Farias, M.A.F. and Mendonça, M. and Soares, H.F. and Kalinowski, M. and Spínola, R.O.},
title={Impacts of agile requirements documentation debt on software projects: A retrospective study},
journal={Proceedings of the ACM Symposium on Applied Computing},
year={2016},
volume={04-08-April-2016},
pages={1290-1295},
doi={10.1145/2851613.2851761},
note={cited By },
url={https://doi.org/10.1145/2961111.2962630},
abstract={Documentation debt is a type of technical debt that describes problems in documentation such as missing, inadequate or incomplete artifacts. Unlike traditional methods, agile methodologies usually employ short iterative cycles and rely on tacit knowledge within a team. In particular, Agile Requirements (AR) (e.g., user stories) tend to reduce the focus on requirements specification activities. This scenario contributes to the occurrence of documentation debt. The goal of this paper is to investigate the impact that this type of debt brings to projects developed by using AR. We address this goal by performing a retrospective study in a real software project that used AR in its development. Our analysis was concentrated on data from 132 maintenance and evolution tasks. Of this total, 65 were related to the presence of documentation debt and were performed within a timeframe of 18 months. The findings indicated an extra maintenance effort of about 47% of the total effort estimated for developing the project and an extra cost of about 48% of the initial cost of the development phase. © 2016 ACM.},
author_keywords={Agile Requirements;  Documentation debt;  Retrospective study;  Technical debt;  User stories},
keywords={Computation theory, Agile Methodologies;  Agile requirements;  Development phase;  Maintenance efforts;  Requirements specifications;  Retrospective study;  Technical debts;  User stories, Iterative methods},
publisher={Association for Computing Machinery},
isbn={9781450337397},
document_type={Conference Paper},
source={Scopus},
}
Downloads: 0