Query: agile requirement management

title: Requirement Management in Agile Software Environment
abstract: Understanding and fulfilling each individual customer requirements has been recognized as a pressing challenge for software industries. To produce high quality software products and meeting stakeholder's requirement is a major challenge in software requirement. Poor requirements and changes to requirements are one of the causes for project overrun and quality issues in the delivered software. The paper discusses about how the different agile methodologies follow requirement management steps in a project. It tries to give an idea to those organizations who undergo projects with frequent change in the requirements so that they can produce quality products and survive in the market strategy.

title: Systematic Literature Review on Decision Making of Requirement Engineering from Agile Software Development
abstract: This paper presents a systematic literature review of agile software development at decision making method for requirement engineering. Presently, agile software development method is operated to cope with requirements that changes dynamically. This study seeks to find out and discuss what types of method that have been exploited for decision making on managing feasible requirements and challenges of decision making in agile software development. Papers reviewed in this study are published from 2017 to present. Resulting 8 papers that have been identified of presenting decision making methods. Using these papers, 11 methods and 7 challenges of decision making identified. This study contributes a review of requirement management and engineering by providing decision making methods on agile software development and the challenges of decision making for requirement engineering.

title: A Review of Requirement Prioritization Techniques in Agile Software Development
abstract: Prioritization is a crucial process in Requirement Change Management (RCM) as erroneous requirements prioritisation may increase the cost of development and lead to project failures. In Agile Software Development (ASD) requirement prioritization (RP) is difficult to maintain and requires more formal process.Changes in the priority list leads towards rework. Moreover, requirement prioritization in Agile is a difficult task due to its volatile nature. Ignorance of critical requirements during prioritization will result in numerous problems like poor quality of product and unsatisfied client. This paper presents a comprehensive review of RP by reviewing the strengths and weaknesses of existing RP techniques.This paper also provides information related to the current state of the art on techniques and practices of RP and the research gaps in related works. These findings will contribute as inputs to construct a framework for selecting suitable RP techniques in ASD which can help software practitioners in choosing suitable prioritization techniques for handling continuous requirement change in ASD.

title: Agile Requirement Engineer Roles and Responsibilities
abstract: Software development in its own is a very complex process and if requirement is not stable and keep changing from the requirement gathering to development phase then it becomes very difficult to implement. Software projects which are getting frequent requirement change and requirements are very dynamic in nature uses agile software development methodology. In this type of software development software requirement management and software configuration management happens to be the most important part. Agile software development needs considerable modification in the software requirement phase, software design phase and coding phase as agile methodology works on iterative manner in this methodology one part of software is analyzed, designed, developed and delivered during each iteration. Traditional requirement engineering and agile requirement engineering are two very different approaches and have their own methods to plan and control requirements. In this paper we will distinguish agile and traditional requirement engineering approaches and we will identify roles and responsibilities of requirement engineering.

title: A survey on product backlog change management and requirement traceability in agile (Scrum)
abstract: Product backlog comprises the outline of desired functionality in a prioritized order in Scrum. Scrum is an iterative, collaborative, and flexible process to develop a software product. Scrum projects welcome changes at any stage of a project, but such changes significantly affect project management activities and quality, including time and budget overrun. These changes also compromise architectural integrity. The objectives of this research were: 1) to determine how product backlog changes are managed by practitioners in Scrum projects, and 2) to explore the perception of practitioners on the use of requirement traceability for product backlog and project risk management during requirement volatility in Scrum. In this research, we conducted a survey among Scrum practitioners and obtained 89 complete responses through our electronic questionnaire. The practitioners identified the reasons of backlog changes and recorded the changed elements. Majority of practitioners recorded modified requirement as "new requirement," but they made changes in the original product backlog. The practitioners tended to agree that requirement traceability was helpful in managing product backlog and minimizing project risk. However, majority of the respondents pointed out the lack of specific requirement traceability method for Scrum.

title: Impact and Challenges of Requirement Engineering in Agile Methodologies: A Systematic Review
abstract: Requirement Engineering is one of important stage in development life cycle. All requirements required for development of product is collected in this phase. A high standard product can be developed by agile methodology in less budget and time. Importance of agile practices have been enhanced since it offers assist cooperation too software engineering. Being basic phase of software engineering, requirement engineering has different processes. The elements of direct correspondence is one of spry way which not at all like to other conventional and traditional approaches .Although a lot of research has been done on agile practices and role of requirement in agile methodologies but still there is need of studies on change manage management ,requirement prioritization, prototyping and nonfunctional requirement in agile methodologies. Aim of this review paper is to present the limitations in presentation of requirement engineering phases in agile practices and what are the issues and challenges that agile person faces in implementation of agile practices. Many research studies from different sources have been reviewed on basis of inclusion and exclusion criteria. Most RE activities has been discussed in review. Evidence helps to prove that how RE process was performed in scrums. Mostly research has been conducted on general agile methodologies, few authors specified RE practices in other methodologies of agile. Finding of this research is the work of researchers that will be beneficial for those who are interested in finding interesting area of research in this field because many techniques of agile (extreme programming, crystal methodology, lean requires further study and practical results as clarified by studies.

title: The Influence of Agile Methodology (Scrum) on Software Project Management
abstract: Software project management has main role in the Software industry. It includes different processes and knowledge areas. The triple constraint of the software project like time, cost and scope is directly dependent on the requirement of the project. Agile methodology is the iterative way for developing the software project for frequent changes, fast delivery and reduce risk. Software project management also plays important role in agile based software project. Agile methodology influence software project management at 10 knowledge areas. In this study we carried out survey from different software companies and it shows that almost every software company uses agile development (Scrum) and has a positive impact on the software project management.

title: Requirement change taxonomy and categorization in agile software development
abstract: Due to the rapid growth in software engineering technology and with advancements of agile methodology, software requirement change management is essentially concerned. Requirements are continuously changed in Agile Software Development (ASD) and need a careful change management method. Continuously change and poorly defined requirements may result in a requirement to become harmful that are both extremely risky and damaging, for the software project in ASD. In order to understand the issue, this paper reviewed several published research papers and identify the requirement change taxonomy. The main objective of this paper is to create requirement change taxonomy and further categorize the requirement change element on the basis of reason and origin of change, for a better understanding of change request. Change categorization will be referred to propose a model of requirement change management in ASD. Moreover, managing change request during requirement change management improves the chance of developing ASD project successfully by minimizing the risks associated with it.

title: Requirement change management in agile offshore development (rcmaod)

title: Using ontology to enhance requirement engineering in agile software process
abstract: One of the most important factors when determining the success of the Agile software development process is requirement engineering. Ontology is a well known knowledge representation tool in knowledge management application. This paper contributes the investigation of its usage in the software development process. We propose the novel use of ontology to enhance requirement engineering in the Agile process to improve communication between software development team and stakeholders.