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:
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.
Table of contents
To score a requirement:
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.
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
Current maintainer:
This module is part of the OCA/business-requirement project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.