featureOS provides two powerful methods, RICE and Value vs. Effort Scoring, to aid in roadmap prioritization, enabling organizations to make well-informed decisions and focus on delivering the most impactful features and improvements.
With a Roadmap's List View you have the flexibility to choose between two prioritization methods: R.I.C.E and Value vs. Effort. You can configure these methods from the individual roadmap's settings.
R.I.C.E Prioritization
RICE = ( Reach * Impact * Confidence ) / Effort
R.I.C.E stands for Reach, Impact, Confidence, and Effort. This method calculates the prioritization score as follows
Reach - Represents the number of people who will actually use the feature, measured as a number.
Impact - Indicates the impact the feature or release will have on your business or organization. You can assign values like 3 for Massive, 2 for High, 1 for Medium, 0.5 for Low, and 0.25 for Minimal.
Effort - Represents the estimated time your team will need to complete the task, measured in days, weeks, or months, depending on the team size and task intensity, expressed as a number.
Confidence - Indicates the level of certainty you have in your estimates, expressed as a percentage from 0 to 100.
Value vs. Effort Prioritization
The Value vs. Effort method is straightforward and simple,
Score = Value / Effort
Value - Represents the business value the feature can bring to your product, rated on a scale of 1 to 5, with 5 being the most valuable.
Effort - Represents the estimation of effort required for the feature, based on input from all team members involved, also rated on a scale of 1 to 5, with 5 being the most effort-intensive.
You can also use the Value vs. Effort's graph view and jump right into achieving your goals.
Pricing & permissions
Multiple Roadmaps with Prioritization is available as a Power-Up, a standalone module not included in any plans. Post-trial you can choose to purchase it on top of your plan (Freeway excluded), for $100/month.
Read more about Multiple Roadmapsβ
Need more help?
Reach out to our support at [email protected] or submit a request on our support board! π
You must be logged in to comment in this article.
Login to comment