Role of Requirements Elicitation &amp; Prioritization to Optimize Quality in Scrum Agile Development

Asghar, Aneesa Rida; Bhatti, Shahid Nazir; Tabassum, Atika; Sultan, Zainab; Abbas, Rabiya

doi:10.14569/ijacsa.2016.071239

Cited by 5 publications

(6 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The requirements prioritization technique mostly increases the value that impacts business success. Until now, numerous techniques have overlooked significant factors that substantially impact requirements prioritization, including cost, value, risk, time to market, the number of requirements, and the influence of non-functional requirements on functional requirements [5], [6]. It is crucial to establish criteria that can estimate the importance of each requirement based on the selected factors [7].…”

Section: Introductionmentioning

confidence: 99%

“…The outcomes revealed six primary categories: benefits, costs, risks, penalties and penalty avoidance, business context, and technical context and requirements characteristic [12], where each category has subcategories accompanied by examples of each. Asghar et al [5] presented a hybrid model for requirements prioritization that combines human decision-making with a critical analysis of factors (sub-characteristics) within the scrum development process. MosCoW was used in the study of Asghar et al [5] to filter requirements by including cost, value, risk, time to market, and effort-required factors.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

A decision tree approach based on BOCR for minimizing criteria in requirements prioritization

Amelia,

Mohamed

2023

IJEECS

View full text Add to dashboard Cite

<span>The requirements selection in the development of a software mostly requires a set of criteria. Determining the criteria used is often confusing because of the many criteria that must match with the characteristics of the project. This study introduces how to classify criteria based on benefits, opportunities, costs, risks (BOCR) to make the requirements prioritization process scalable. Project context characteristics and stakeholder perspectives are essential points discussed in this study because they are crucial in the requirements prioritization process. The criteria obtained from the literature review were followed by a survey to determine the importance of the criteria and their grouping in the BOCR using the decision tree method. There are 38 criteria and are grouped into four categories. There are two very significant criteria with a high level of importance, namely business value and stakeholder satisfaction. A decision tree based on BOCR can be used to classify the criteria for requirements prioritization. This research contributes to assisting software developers in finding and determining the criteria operated during the prioritization of requirements. Additionally, it is important to consider the project context and the collaboration the client and developer when prioritizing requirements.</span>

show abstract

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

A decision tree approach based on BOCR for minimizing criteria in requirements prioritization

Amelia,

Mohamed

2023

IJEECS

View full text Add to dashboard Cite

show abstract

“…In agile software development (ASD), where late changes in requirements are welcomed to meet dynamic demands of businesses, QRs are usually underspecified or undocumented, and not considered early enough in the software development cycle as functional requirements [26]. In such cases, their mistreatment may result in project failure or loss [27].…”

Section: Introductionmentioning

confidence: 99%

Documentation of Quality Requirements in Agile Software Development

Behutiye

Seppänen

Rodríguez

et al. 2020

Proceedings of the Evaluation and Assessment in Software Engineering

View full text Add to dashboard Cite

Context: Quality requirements (QRs) have a significant role in the success of software projects. In agile software development (ASD), where working software is valued over comprehensive documentation, QRs are often under-specified or not documented. Consequently, they may be handled improperly and result in degraded software quality and increased maintenance costs. Investigating the documentation of QRs in ASD, would provide evidence on existing practices, tools and aspects considered in ASD that other practitioners might utilize to improve documentation and management of QRs in ASD. Although there are some studies examining documentation in ASD, those that specifically investigate the documentation of QRs in depth are lacking. Method: we conducted a multiple case study by interviewing 15 practitioners of four ASD cases, to provide empirical evidence on documentation of QRs in ASD. We also run workshops with two of the cases, to identify important aspects that ASD practitioners consider when documenting QRs in requirements management repositories. Result and conclusions: ASD companies approach documentation of QRs to fit the needs of their context. They used tools, backlogs, iterative prototypes, and artifacts such as epic, and stories to document QRs, or utilized face-face communication without documenting QRs. We observed that documentation of QRs in ASD is affected by factors such as context (e.g. product domain, and size) and the experience of practitioners. Some tools used to document QRs also enhanced customer collaboration, enabling customers report and document QRs. Aspects such as levels of abstraction, the traceability of QRs, optimal details of information of QRs and verification and validation are deemed important when documenting QRs in ASD requirements management repositories.

show abstract

“…It states the "what" and "why" of the system. Requirement elicitation is one of the most important phases of the software development life cycle because project's initiation is largely dependent on it (Rida et al, 2016). There can be various reasons for the project failure but one of the main reasons for the project failure is due to the various requirement issues like less customer involvement, unclear expectations of the customer or any changes to the requirements.…”

Section: Introductionmentioning

confidence: 99%

“…Thus, many types of software process models were introduced which focus on various aspects of software processes like product, activity, resource etc but none of them focuses on social aspect of a project such as motivation for performing a task, what skills are required and what are the dependencies among the team members. i* modelling framework which is based on the concept of "intentional actor" was developed for analysing and relating the social and human aspects (Rida et al, 2016).…”

Section: Introductionmentioning

confidence: 99%

Enhancing Quality in Agile Requirement Elicitation Process

Kaur

Bhuiyan²,

Prasad

et al. 2019

American Journal of Applied Sciences

View full text Add to dashboard Cite

Eliciting requirements is one of the key aspects of the software development life cycle. Incorrect determination of the requirements can lead to the failure of the projects. Traditional waterfall method does not accommodate changing requirements easily while agile methodology welcomes the changing requirements even at the later phases of the development life cycle. The aim of the research is to improve the agile requirement elicitation process to ensure quality product is developed that aligns to the organizational strategy and its high value initiatives. Requirement elicitation process within agile projects should consider organisational actor's strategic dependency and rationale to ensure alignment with organisational strategy. We propose to improve the requirement elicitation process by combining i*organizational models with standard Agile-Scrum methodology through a real-life health service provider scenario. The aim of our methodology is to ensure the social aspects of the organizational actor's strategic dependency and rationale are considered. We argue the requirement process could be significantly improved by combining these two aspects; Agile-Scrum methodology will address the requirements through user stories, vision document, epics and i*organizational model will include the social aspects of the organization to reduce the gap between the project goal and organization goal.

show abstract

Role of Requirements Elicitation & Prioritization to Optimize Quality in Scrum Agile Development

Cited by 5 publications

References 10 publications

A decision tree approach based on BOCR for minimizing criteria in requirements prioritization

A decision tree approach based on BOCR for minimizing criteria in requirements prioritization

Documentation of Quality Requirements in Agile Software Development

Enhancing Quality in Agile Requirement Elicitation Process

Contact Info

Product

Resources

About