Role of Requirements Elicitation and Prioritization to Improve the Quality in Scrum Agile Development (T-0726) (MFN 6190)

Abstract

Agile methodology is an innovative and iterative process that supports changing requirements and helps in addressing changes throughout the development process. Requirements are elicited at the beginning of every software development process and project (product) and latter are prioritized according to their importance to the market and to the product itself. One of the most important and influencing steps while making a software product is requirements prioritization. Prioritizing requirements helps the software team to understand the existence and importance of a particular requirement, there are several requirements prioritization methodologies that aid in decision making but importantly many lacks to account the important factors that have significant influence in prioritizing requirements. In (Scrum) sprints, requirements will be prioritized both on the basis of influencing factors such as cost, value, risk, time to market etc. and through the effect of non-functional requirements over functional requirements. We have proposed a requirement prioritization methodology (model) based on several factors such as time to market, cost, risk etc. The proposed model is expected to overcome this lack. This will improve the overall quality of software product when it is included in the development process of scrum. Requirements will not only be prioritized based on sprints, human decision but by critically analyzing the factors (sub characteristics) that can cause the product to success/ fail repeatedly thus ensuring the consistency in right requirements and hence the right prioritized requirements will sbe selected for a particular sprint at a time. The quagmire results via different case studies indicate that time and human behavioral factor plays an important role in making accurate/ reliable requirements prioritization decisions that will require minimal changes throughout the development process as customers/stakeholders or development team members as well as PO are thoroughly involved in the development process.