An Agile Method of Representing, Organizing, and (Re) Prioritizing Requirements in a Large Enterprise

Abstract

Agile and lean are now the mainstream tenets of software development. This development methodology is attracting attention because it can develop software that operates quickly despite uncertain situations and limited information (requirements), and it can adaptively develop while checking feedback both frequently and regularly. The key is to welcome change without resistance, which is not limited to development but also requires changes in requirement management. However, there is a lack of practical guidance on how to manage changes in agile requirements engineering. Although we need to consider all areas of requirements engineering, the author has seen three key themes: (1) How to focus on customer value and represent it clearly for smooth communication between teams in a large enterprise? (2) What are the requirements for organizing elements that make it easy to accept changes and assess impacts? (3) What reasonable algorithm is easy to use and reliable to prioritize or reorder requirements based on values regularly? The author wants to suggest practical ways to address these themes and propose a way to deal with three themes without compromising on the essence of agile. The author is going to do case studies with some organizations that are already using or first adopting agile software development. The author could get the strengths and weaknesses in terms of collaboration promotion and change both the acceptance and qualitative feedback on application results.