Follow
EmailIn our last post on this blog, we talked about how ROI Metric can be very helpful to product managers in prioritizing requirements and feature requests.
In this post, we’d like to outline some practical steps that PMs can use to get started with this practice…
Practical Steps
- Create a list of all the major benefits to your organization that implementing new requirements and features can produce. Examples, as mentioned in our last post, include:
- Build customer loyalty
- Create competitive advantage
- Further business strategy
- …
- And, of course, financial benefits: Increase revenue & profits
- Give each of these benefits an appropriate weighting.
- For each requirement/feature under consideration, assign a value to each benefit on a scale of 1-10.
- Calculate the weighted sum of all the benefits. This is the “Total Return” of a given requirement.
- Assign a value to the “Investment” needed to implement the requirement, again on a scale of 1-10.
- Divide “Total Return” by “Investment” to calculate ROI Metric for the requirement.
Once you normalize this ROI metric, you can then use it to prioritize your requirements and features in your next MRD (Market Requirements Document) or PRD (Product Requirements Document). This will help you implement a structured method to prioritize your requirements.
We believe that this type of a structured methodology is much more repeatable and defensible than ad-hoc judgments often used to prioritize requirements and features.
Editor’s Note:
Interested in an affordable, enterprise-quality software to help you manage requirements in a better way? Check out FREE 30-Day trial of Accompa or Sign Up for a Demo.
Like This Post? Get More by Email
3) Do not read this blog one sentence per day during your lunch break, while eating a 