Impacts of agile requirements documentation debt on software projects

Mendes, Thiago Souto; Farias, Mário André de Freitas; Mendonça, Manoel; Soares, Henrique Frota; Kalinowski, Marcos; Spínola, Rodrigo O.

doi:10.1145/2851613.2851761

Cited by 19 publications

(12 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Os protótipos também ocupam uma posição de destaque, já que eles, conforme os autores Käpyaho e Kauppinen [20], ajudam a enfrentar alguns desafios da engenharia de requisitos ágil. Diversos estudos apresentam o uso de uma ferramenta de apoio às atividades de ER ( [8], [10], [12], [16], [17], [21], [31] e [40]). Foram encontradas referências a 21 ferramentas diferentes, sendo poucas repetidas em mais de um artigo.…”

Section: Tabela 2 Distribuição Dos Métodos Deunclassified

“…Outro benefício que deve ser destacado é a melhora no entendimento os requisitos. Apesar de vários benefícios reportados, há trabalhos que observaram em suas lições aprendidas criticando o fato de que a documentação em projetos ágeis nem sempre é suficiente e que existe débito de documentação de requisitos, por exemplo esses trabalhos: [20], [21], [28], [31], [38] e [40]. Benefícios reportados pelo uso de métodos ágeis relacionados às atividades de ER envolvem melhoria da comunicação e compreensão das necessidades, redução da ambiguidade e capacidade de responder a mudanças.…”

Section: Tabela 2 Distribuição Dos Métodos Deunclassified

“…Isso se torna um desafio para desenvolvimento de software e em alguns casos a documentação e os requisitos se tornam obsoletos antes mesmo do término do projeto [19]. No estudo feito por Mendes e outros [31] foram analisadas 132 tarefas de manutenção e evolução em projetos ágeis. Em 65 dessas, foram notados débitos de documentação.…”

Section: Introductionunclassified

See 2 more Smart Citations

A Engenharia de Requisitos nos métodos ágeis: uma revisão sistemática da literatura

Fraga

Barbosa

2017

Anais Do Simpósio Brasileiro De Sistemas De Informação (SBSI)

View full text Add to dashboard Cite

Belo Horizonte -MG -Brasil mwerneck@pucminas.br RESUMOPor não possuírem características prescritivas, não há, nos métodos ágeis, uma definição formal sobre como as atividades de Engenharia de Requisitos (ER) devem ser executadas. Isso faz com que haja uma variedade de formas de se definir como serão levantados, priorizados, especificados e validados os requisitos. Assim, torna-se necessário compreender como as pesquisas em ER ágil têm caracterizado estas atividades. O objetivo deste trabalho foi, por meio de uma revisão sistemática da literatura, identificar as práticas e técnicas utilizadas para cada processo da ER em projetos ágeis. O trabalho identificou ainda importantes desafios e lições aprendidas que devem direcionar as evoluções nesta área. ABSTRACTSince agile methods do not have prescriptive characteristics, there is not a formal definition on how Requirements Engineering (RE) activities should be executed. This situation leads to a variety of different forms of defining how requirements are elicited, prioritized, documented and validated. So, it is necessary to comprehend how research on RE have characterized such activities. By using a systematic review approach, the objective of this study was to identify practices and techniques that have been used for each RE process in agile projects. The study also identified challenges and lessons learned that should direct improvements in this area. CCS Concepts• Software and its engineering Software creation and management Software development process management Agile software development • Software and its engineering Software creation and management Designing Software Requirements Analysis.

show abstract

Section: Tabela 2 Distribuição Dos Métodos Deunclassified

See 1 more Smart Citation

A Engenharia de Requisitos nos métodos ágeis: uma revisão sistemática da literatura

Fraga

Barbosa

2017

Anais Do Simpósio Brasileiro De Sistemas De Informação (SBSI)

View full text Add to dashboard Cite

show abstract

“…In such cases, developers face time pressure, mainly focus on delivery of functionalities and often do not give consideration to NFRs [6]. However, in such scenarios, neglecting NFRs may result in documentation debt with further consequences of increase in maintenance cost and effort [16].…”

Section: Introductionmentioning

confidence: 99%

Non-functional Requirements Documentation in Agile Software Development: Challenges and Solution Proposal

Behutiye

Karhapää

Costal

et al. 2017

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Non-functional requirements (NFRs) are determinant for the success of software projects. However, they are characterized as hard to define, and in agile software development (ASD), are often given less priority and usually not documented. In this paper, we present the findings of the documentation practices and challenges of NFRs in companies utilizing ASD and propose guidelines for enhancing NFRs documentation in ASD. We interviewed practitioners from four companies and identified that epics, features, user stories, acceptance criteria, Definition of Done (DoD), product and sprint backlogs are used for documenting NFRs. Wikis, word documents, mockups and spreadsheets are also used for documenting NFRs. In smaller companies, NFRs are communicated through white board and flip chart discussions and developers' tacit knowledge is prioritized over documentation. However, loss of traceability of NFRs, the difficulty in comprehending NFRs by new developers joining the team and limitations of documentation practices for NFRs are challenges in ASD. In this regard, we propose guidelines for documenting NFRs in ASD. The proposed guidelines consider the diversity of the NFRs to document and suggest different representation artefacts depending on the NFRs scope and level of detail. The representation artefacts suggested are among those currently used in ASD in order not to introduce new specific ones that might hamper actual adoption by practitioners.

show abstract

“…In other words, there are more information from the customer point of view written in a too high level than from the developers perspective, with some implementation details. Moreover, user stories might reflect in documentation debt [5], which can cause significant impact in terms of maintenance effort and cost in agile software development projects, which drive developers to misunderstanding. Thus, it could be detailed and to continue in high level.…”

Section: Introductionmentioning

confidence: 99%

Cosmic User Story Standard

Ecar

Kepler

Silva

2018

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Abstract. User Story is a technique widely used in Agile development. It is characterised as short and high level descriptions of required functionality, written in customer language during the very early requirement gathering stage and containing just enough information to produce the estimated implementation effort. The COSMIC method is a second generation technique for function size measurement. The requirement estimation precision in COSMIC is directly proportional to the requirement detailing level. Current templates for user stories writing might ignore important information for COSMIC measurement purposes. This paper introduces a new template for writing user stories which is more expressive in terms of COSMIC size estimation. We performed a qualitative survey to introduce this new user story template to the COSMIC community, intending to capture the COSMIC users opinion in terms of expressiveness and how valuable it is. The survey points to promising results considering the COSMIC users opinion about the new template. This study contributes to agile requirements from the COSMIC users point of view. This new template may be a step forward in terms of user story estimation for COSMIC sizing based projects.

show abstract

Impacts of agile requirements documentation debt on software projects

Cited by 19 publications

References 9 publications

A Engenharia de Requisitos nos métodos ágeis: uma revisão sistemática da literatura

A Engenharia de Requisitos nos métodos ágeis: uma revisão sistemática da literatura

Non-functional Requirements Documentation in Agile Software Development: Challenges and Solution Proposal

Cosmic User Story Standard

Contact Info

Product

Resources

About