Defining agile requirements change management

Albuquerque, Danyllo; Guimarães, Everton; Perkusich, Mirko; Costa, Alexandre; Dantas, Emanuel; Ramos, Felipe; Almeida, Hyggo

doi:10.1145/3341105.3374095

Cited by 13 publications

(8 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In addition to these challenges, in our earlier work we found that RCs in agile contexts are challenging to handle when their complexity is high, cascading impact is high, size is large, the effort required is high, the definition is imprecise or unclear, the priority is high, the access to customer is difficult or irregular, and the cross-functionality is forced [16]. Even though there are practices (e.g., face-to-face communication [17], [18], [19], [20] iterative requirements [21], [22], [20] [19], prototyping [21], [22], [23] review meetings [22], [19], and prioritisation [21], [22], [19], see Table 2) that are available to mitigate these challenges and handle RCs, most of these challenges result in varying emotional responses in software practitioners [3], [16].…”

Section: Requirements Change Handlingmentioning

confidence: 99%

The Role of Emotional Intelligence in Handling Requirements Changes in Software Engineering

Madampe¹,

Hoda²,

Grundy³

2022

Preprint

View full text Add to dashboard Cite

Background: Requirements changes (RCs) are inevitable in Software Engineering. Research shows that emotional intelligence (EI) should be used alongside agility and cognitive intelligence during RC handling. Objective: We wanted to study the role of EI in-depth during RC handling. Method: We conducted a socio-technical grounded theory study with eighteen software practitioners from Australia, New Zealand, Singapore, and Sri Lanka. Findings: We found causal condition (software practitioners handling RCs), intervening condition (mode of work), causes (being aware of own emotions, being aware of others' emotions), direct consequences (regulating own emotions, managing relationships), extended consequences (sustaining productivity, setting and sustaining team goals), and contingencies: strategies (open and regular communication, tracking commitments and issues, and ten other strategies) of using EI during RC handling. We also found the covariances where strategies co-vary with the causes and direct consequences, and ease/ difficulty in executing strategies co-vary with the intervening condition. Conclusion: Open and regular communication is key to EI during RC handling. To the best of our knowledge, the framework we present in this paper is the first theoretical framework on EI in Software Engineering research. We provide recommendations including a problem-solution chart in the form of causes, direct consequences, and mode of work against the contingencies: strategies for software practitioners to consider during RC handling, and future directions of research.

show abstract

Section: Requirements Change Handlingmentioning

confidence: 99%

The Role of Emotional Intelligence in Handling Requirements Changes in Software Engineering

Madampe¹,

Hoda²,

Grundy³

2022

Preprint

View full text Add to dashboard Cite

show abstract

“…Albuquerque et al [116] stated that there are a lot of ways to enhance the requirement change management in agile system development. ey further proposed a study which describes agile requirement change management (ARCM) process and activities associated to this process in order to manage the requirement change in agile modeling.…”

Section: Requirement Managementmentioning

confidence: 99%

“…According to Albuquerque et al [116], the process of agile requirement change management consists of requirement change identification, analysis, cost, and effort estimation to handle and manage change in requirements. AbdElazim et al [93] presented a framework to prioritize the requirements in agile development which consists of four stages: identification, verification, estimation, and prioritization.…”

Section: Requirement Specification and Changementioning

confidence: 99%

Requirement Engineering Challenges in Agile Software Development

Rasheed

Zafar

Shehryar

et al. 2021

Mathematical Problems in Engineering

View full text Add to dashboard Cite

Agile software development has large success rate due to its benefits and promising nature but natively where the size of the project is small. Requirement engineering (RE) is crucial as in each software development life cycle, “Requirements” play a vital role. Though agile provides values to customer’s business needs, changing requirement, and interaction, we also have to face impediments in agile, many of which are related to requirement challenges. This article aims to find out the challenges being faced during requirement engineering of agile projects. Many research studies have been conducted on requirement challenges which are somehow biased, no suggestions are given to improve the agile development process, and the research does not highlight large-scale agile development challenges. Hence, this article covers all the challenges discussed above and presents a comprehensive overview of agile models from requirement engineering perspective. The findings and results can be very helpful for software industry to improve development process as well as for researchers who want to work further in this direction.

show abstract

“…Other studies only addressed sub-problems. For instance, Albuquerque et al deal with agile requirements engineering [4]. The authors considered 14 different agile practices in their mapping study.…”

Section: Background and Related Workmentioning

confidence: 99%

The Integrated List of Agile Practices -- A Tertiary Study

Neumann¹

2021

Preprint

View full text Add to dashboard Cite

Context: Companies adapt agile methods, practices or artifacts for their use in practice since more than two decades. This adaptions result in a wide variety of described agile practices. For instance, the Agile Alliance lists 75 different practices in its Agile Glossary. This situation may lead to misunderstandings, as agile practices with similar names can be interpreted and used differently. Objective: This paper synthesize an integrated list of agile practices, both from primary and secondary sources. Method: We performed a tertiary study to identify existing overviews and lists of agile practices in the literature. We identified 876 studies, of which 37 were included. Results: The results of our paper show that certain agile practices are listed and used more often in existing studies. Our integrated list of agile practices comprises 38 entries structured in five categories. Contribution: The high number of agile practices and thus, the wide variety increased steadily over the past decades due to the adaption of agile methods. Based on our findings, we present a comprehensive overview of agile practices. The research community benefits from our integrated list of agile practices as a potential basis for future research. Also, practitioners benefit from our findings, as the structured overview of agile practices provides the opportunity to select or adapt practices for their specific needs.

show abstract

Defining agile requirements change management

Cited by 13 publications

References 18 publications

The Role of Emotional Intelligence in Handling Requirements Changes in Software Engineering

The Role of Emotional Intelligence in Handling Requirements Changes in Software Engineering

Requirement Engineering Challenges in Agile Software Development

The Integrated List of Agile Practices -- A Tertiary Study

Contact Info

Product

Resources

About