Prioritizing User Requirements for Agile Software Development

With the accelerating rising business needs and also developing technology, user requirements evolve almost every day due to which they cannot be perfected at once. Therefore, agile methodology helps in modeling these user requirements through user stories iteratively and incrementally. However, this can only be done through continuous prioritization. This prioritization is essential for meeting the budgetary constraints and time to market deadlines, and is done by the Product Owner (PO) on the basis of Business Value without considering the dependence of one story on other due to execution order. This dependence can be understood by visualizing the process flow using UML Activity Diagram. The conversion of user requirements into UML Diagram can be done via NLP. Once the UML is ready, it helps to prioritize the stories according to process flow. This paper aims to provide an approach to tackle the issue of prioritization considering both the business value and process flow aspects and help the PO in making decisions about which requirements to be considered first and arranging them in Product Backlog.