Abstract

In Agile changes may be made at any time throughout the project lifetime in agile projects. These changes, however, often lead to longer turnaround times and higher costs while having a substantial influence on the activities and quality of project management. The suggested framework's main goal is to increase the effectiveness and flexibility of the requirement engineering process by successfully managing requirements changes, particularly in contexts where Agile Software Development (ASD) is practiced. The Agile methodology has gained popularity as a strategy for developing software because it can adjust to changing requirements and deliver software gradually. To make sure that the software being produced satisfies stakeholder expectations and adds value to the firm, good requirement management is essential. Using the Analytic Hierarchy Process (AHP) to prioritize requirements based on their relative relevance and urgency, this article introduces a framework for requirement management in Agile Projects. The most important requirements are taken care of first thanks to this strategy, which enables a more organized and informed decision-making process. We demonstrate the actual use of our framework in real-world contexts and highlight its efficacy in solving the issues faced by Agile projects by including a case study and an accompanying table. The suggested framework also supports the three core tenets of the Agile approach—transparency, cooperation, and continuous improvement—to foster an environment of excellence and ongoing learning within the Agile team. By developing these fundamental ideas, our framework not only supports Agile teams' continual growth and development but also helps them manage and prioritize requirements more efficiently, which ultimately improves project results and increases organizational value.

Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call