Business Requirement RICE
This module lets you prioritise business requirements with the RICE scoring model, which is useful when you collect more requests than you can work on and need to decide which ones to address first.
The score combines four estimates:
- Reach: how many users or events are affected over a given period.
- Impact: how much each affected user benefits, from minimal to massive.
- Confidence: how sure you are about your reach and impact estimates.
- Effort: the total work needed, usually in person-months.
They are combined as Reach x Impact x Confidence / Effort, so a requirement that reaches many users for little work ranks above one that reaches few for a lot of work. The resulting score is stored, which means you can sort and group your requirements by it.
The priority field of the requirement is left untouched, so you can keep using it alongside the score.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Adds a RICE scoring section to business requirements so you can rank requests by Reach x Impact x Confidence / Effort. The score is stored, shown in the form, list and kanban views, and can be used to filter and sort requirements.
This module extends the existing business requirement feature with a prioritisation score based on the RICE model. On each requirement you get a new "RICE" tab where you enter four estimates: Reach (a whole number, for example how many users are affected per quarter), Impact (Minimal, Low, Medium, High or Massive, defaulting to Medium), Confidence (Low 50%, Medium 80% or High 100%, defaulting to Medium) and Effort (a number, usually person-months, defaulting to 1).
Odoo then automatically calculates the RICE Score as Reach x Impact x Confidence / Effort. The score is saved on the record, so you can sort and group requirements by it. If Reach is negative or Effort is zero or negative, the score is set to 0 instead of producing a meaningless result.
Where you see it: - A dedicated RICE tab on the requirement form. - A RICE Score column in the requirements list, shown after the priority column. - The score displayed on the kanban card when it is greater than zero. - A "Scored" filter in the search bar that keeps only requirements with a score above zero.
The standard priority field is not changed, so you can keep using it alongside the RICE score. All of this applies to the business.requirement model.
Depends on
Models and fields (1)
- business.requirement · extends an existing modelrice_reach (Reach), rice_score (RICE Score), rice_effort (Effort), rice_impact (Impact), rice_confidence (Confidence)
Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/business-requirement.
terminal Installation and usage
OCA documentation · Odoo 18.0Usage
Source · Odoo 18.0To score a requirement:
- Go to Business Requirements and open or create a requirement.
- Go to the RICE tab and fill in reach, impact, confidence and effort.
- The score is computed as you fill them in.
To prioritise your requirements, go to the list view and sort by the RICE Score column, or use the Scored filter to leave out the requirements nobody has estimated yet. Reach, impact, confidence and effort are all optional: a requirement nobody has estimated simply scores zero.
Requirements with an effort of zero score zero, so an unestimated effort never sends a requirement to the top of the list. A negative reach or effort scores zero as well, since neither is a usable estimate.
No verified information in OCA: Installation, Configuration.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.