How to order large amount of business requirements properly?
irl last edited by
We continuously develop, operate and maintain a hardware-software system. The last year a load of complex business requirement (100-150) is accumulated but unfortunately not processed well. The current goal of our BA-s to prioritize somehow this list and/or add some business value on it. I want to add some intention about the BA-s, how to order this amount of requirements. The client has no KPI assigned to the requirements.
The most promising is the MoSCoW method, but I assume that our client could not be effective this amount of requirements. Is there any best practice how to resolve this situation?
There is a bunch of techniques to prioritize your backlog. Scoring models (value vs effort, value vs complexity, RICE etc), KANO, MoSCoW, adoption of Delphi method (Buy a feature, Cost of delay), yadayadayada.
The successful application of prioritization framework depends from your situation. If you have a dedicated person who can justify all business needs, you should have no any issues. Just give this person title "Product Owner" and explain him Business Value concept.
Your team have pipeline about 100 change requests per year (2-3 per week), most probably you operates with bunch of different stakeholders (hopefully whey are not conflicting). The real challenge is how to align such amount of people around the similar priorities understanding. In my practice in such situations the "Cost of delay" method was most successful. This concept is pretty clear for most of the business people since it's explains everything on their native language. For reference you may check how WSJF matrixes in SAFe have been designed, it's very practical.
Here is good read about existing techniques. https://roadmunk.com/blog/product-prioritization-techniques/
And, btw, congratulations. If someone send you 2-3 change requests per week, it means the business people is really interested in your job