The 12-Point Requirements Prioritization Framework
Arvind has more than 13 years of progressive experience in software development, which includes project management, business analysis and planning, development, implementation and quality orientation.
When it comes to the process of assigning a requirement’s priority, any requirement may be prioritized at any point in its lifecycle, according to A Guide to the Business Analyst’s Body of Knowledge®. BABOK Guide 2.0 devotes a whole section to prioritizing requirements, noting, “Prioritization of requirements ensures that analysis and implementation efforts focus on the most critical requirements.”1
Numerous methods on how to prioritize requirements have been developed and debated. While some work best on a small number of requirements, others are better suited to very complex projects with many decision makers. Before a requirement can be prioritized, an analyst must consider why it is the most important from a business standpoint—and what its impact would be on the overall system. There are a number of possible business considerations (including value, cost, risk, improving customer experience, stakeholder agreement and urgency variables), but most all prioritization methods focus on the “Why” factor (Why is the work important?2).
Prioritizing business requirements requires a holistic approach. The approach has to be framed on a set of principles and a mathematical model linked together through a consistent framework—while also ensuring the outcome is aligned with the long-term business goals, IT strategy and in-flight…
Please log in or sign up below to read the rest of the article.
ADVERTISEMENT
Published at Mon, 25 Jun 2018 04:00:00 +0000
