Abstract:
The following research work is based on requirements prioritization techniques and
relationship in context of the modern software development methodologies (Agile, Scrum,
Extreme Programming) and precisely how these requirements are prioritized systematically in
sprints (cycles) based on different aspects (Cost, Value, Risk, and Time factors). As Agile
Software Development (AGSD) plays a vibrant role in software engineering, it involves
customer in the real time with new or change requirements, while within the scope of the
software(s) development, which further offer instant changes in the requirements besides
software requirements are a foremost part of a project to be executed in successive manner.
Requirements elicitation, prioritizing and management is done throughout the product life
cycle as it should done with proper correspondence and coordination between the developer,
customer and importantly the agile team to build up effective conclusion. In agile software
engineering changes occur in iterative manner, thus there is a major challenge for the
managers to prioritize the new requirements that occur in the product backlog and sprint
backlog. Different requirements prioritization techniques are used for this purpose and they
mostly lack to prioritize the novel user stories (iterations) which befall in the backlog, as
comprehensively highlighted in the section literature review. Further focus of this work is
finding out which are the core, primary factors which mark the performance of agile team,
and delinquent that product manager faces during the backlog requirements prioritization and
importantly how these said requirements iterations can be prioritize in effective manner. To
overcome this challenge of effective and efficient requirements prioritization a hybrid
requirements prioritization model is proposed in this research work which will be able to
effectively handle the new and backlog requirements in scrum agile methodology as a test
case scenario.
