[et_pb_section fb_built=”1″ _builder_version=”4.4.1″ background_color=”#fbfcfd” global_module=”1099″ global_colors_info=”{}”][et_pb_row column_structure=”1_2,1_2″ disabled_on=”on|on|off” _builder_version=”4.16″ global_colors_info=”{}”][et_pb_column type=”1_2″ _builder_version=”4.16″ global_colors_info=”{}”][et_pb_image src=”https:\/\/agilecoach.ee\/wp-content\/uploads\/2020\/01\/Merle-black-and-white-round-less-shiny-1.png” _builder_version=”4.16″ custom_margin=”-5%|||25%|false|false” custom_css_main_element=”-webkit-clip-path: circle(50% at 50% 50%);||clip-path: circle(50% at 50% 50%);||width: 75px;||height: 75px;” global_colors_info=”{}”][\/et_pb_image][\/et_pb_column][et_pb_column type=”1_2″ _builder_version=”4.16″ global_colors_info=”{}”][et_pb_text _builder_version=”4.16″ text_font=”Source Sans Pro||||||||” text_text_color=”rgba(0,0,0,0.8)” custom_margin=”-3%|||-60%|false|false” global_colors_info=”{}”]<\/p>\n
Merle Randlepp<\/p>\n
[\/et_pb_text][et_pb_text _builder_version=”4.16″ text_font=”Source Sans Pro||||||||” text_text_color=”rgba(0,0,0,0.44)” custom_margin=”-5%|||-60%|false|false” global_colors_info=”{}”]<\/p>\n
Agile Coach<\/p>\n
[\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row disabled_on=”off|off|on” _builder_version=”4.16″ global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.16″ global_colors_info=”{}”][et_pb_image src=”https:\/\/agilecoach.ee\/wp-content\/uploads\/2020\/01\/Merle-black-and-white-round-less-shiny-1.png” align=”center” _builder_version=”4.16″ custom_margin=”||||true|false” custom_css_main_element=”-webkit-clip-path: circle(50% at 50% 50%);||clip-path: circle(50% at 50% 50%);||width: 75px;||height: 75px;” global_colors_info=”{}”][\/et_pb_image][et_pb_text _builder_version=”4.16″ text_font=”Source Sans Pro||||||||” text_text_color=”rgba(0,0,0,0.8)” text_orientation=”center” custom_margin=”-3%||||false|false” global_colors_info=”{}”]<\/p>\n
Merle Randlepp<\/p>\n
[\/et_pb_text][et_pb_text _builder_version=”4.16″ text_font=”Source Sans Pro||||||||” text_text_color=”rgba(0,0,0,0.44)” text_orientation=”center” custom_margin=”-3%||||false|false” global_colors_info=”{}”]<\/p>\n
Agile Coach<\/p>\n
[\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.17.6″ global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.16″ global_colors_info=”{}”][et_pb_post_title author=”off” comments=”off” featured_image=”off” _builder_version=”4.16″ title_font=”Source Sans Pro|700|||||||” title_text_align=”center” title_text_color=”rgba(0,0,0,0.8)” title_font_size=”47px” text_orientation=”center” title_font_size_tablet=”40px” title_font_size_phone=”35px” title_font_size_last_edited=”on|desktop” global_colors_info=”{}”][\/et_pb_post_title][et_pb_text _builder_version=”4.16″ _module_preset=”default” text_font=”Source Sans Pro||||||||” text_font_size=”15px” text_line_height=”1em” text_orientation=”right” custom_margin=”|||10%|false|false” global_colors_info=”{}”]
In product development, we never have enough time or resources to implement all desired initiatives. Product owners constantly evaluate which developments to pursue and which to postpone, and making the right decisions is far from easy. The RICE model helps us make faster and more accurate decisions when prioritizing tasks.<\/strong> In this blog post, I will discuss the usefulness, structure, adaptation, and implementation of the RICE model. Here you will also find several tools: a RICE model table, workshop instructions for creating the model, and a model cheat sheet<\/a>. <\/p>\n The art of prioritization is one of the most critical activities in product development. However, we should not pose the question as \u201cIs this development idea good or bad?\u201d but rather \u201cWhich sequence of development tasks creates the most business value?<\/strong>\u201d. <\/p>\n Therefore, it is important to use a specific prioritization method in product development and not rely solely on gut feelings when making decisions. There are many different prioritization techniques, and the RICE model is one of the most popular in software development. <\/p>\n [\/et_pb_text][et_pb_image src=”https:\/\/agilecoach.ee\/wp-content\/uploads\/2024\/03\/Prioritization-Different-Methods-scaled.jpeg” title_text=”Prioritization – Different Methods” show_in_lightbox=”on” align=”center” _builder_version=”4.24.2″ _module_preset=”default” global_colors_info=”{}”][\/et_pb_image][et_pb_text disabled_on=”off|off|off” _builder_version=”4.24.2″ text_font=”Source Sans Pro|300|||||||” text_text_color=”rgba(0,0,0,0.89)” text_font_size=”16px” text_orientation=”center” custom_margin=”-1%||||false|false” custom_padding=”0px||||false|false” global_colors_info=”{}”]<\/p>\n Different prioritization methods. Image by author. <\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.24.2″ _module_preset=”96fa8149-2d7e-4fe7-bc52-734658dc4791″ max_width_phone=”800%” max_width_last_edited=”off|phone” custom_margin_tablet=”|||5%|false|false” custom_margin_phone=”|||5%|false|false” custom_margin_last_edited=”on|desktop” global_colors_info=”{}”]<\/p>\n Setting priorities is a complex task because there are so many different factors to consider. We must consider the interests of our clients and end-users, the business interests of the company, as well as technical aspects such as innovation, speed, reliability, and more. <\/p>\n With so many different factors, it is natural that without a clear method, discussions can take an unreasonable amount of time<\/strong>, and ultimately, there is still no certainty about the correctness of the decisions made.<\/p>\n Too often, I have seen a list of development tasks (Product Backlog<\/em>) whose top consists of about 50 tasks with a \u201chigh\u201d priority. How then to choose which of these 50 tasks to tackle next? Many prioritization methods only help us categorize<\/strong> development tasks (e.g., high\/medium\/low priority), but they do not provide us with the order in which tasks should be performed<\/strong>. <\/p>\n Furthermore, comparing development tasks often seems like an \u201capples and oranges\u201d problem<\/strong>, because qualitative assessments are difficult to provide and justify.<\/p>\n Therefore, if we find a way to put qualitative information into a numerical model, it will help us achieve our ultimate goal: to determine the best order for development tasks<\/strong>.<\/p>\n<\/blockquote>\n For this, there is no need to create an overly complex model that considers dozens of different factors. There is a much simpler way, and that is the RICE model adapted to your needs. <\/p>\n [\/et_pb_text][et_pb_image src=”https:\/\/agilecoach.ee\/wp-content\/uploads\/2024\/03\/RICE-calculation-formula-scaled.jpeg” title_text=”RICE calculation formula” show_in_lightbox=”on” align=”center” _builder_version=”4.24.2″ _module_preset=”default” global_colors_info=”{}”][\/et_pb_image][et_pb_text disabled_on=”off|off|off” _builder_version=”4.24.2″ text_font=”Source Sans Pro|300|||||||” text_text_color=”rgba(0,0,0,0.89)” text_font_size=”16px” text_line_height=”1em” text_orientation=”center” custom_margin=”-1%||||false|false” custom_padding=”0px||||false|false” global_colors_info=”{}”]<\/p>\n RICE score calculation formula. Image by author. <\/a><\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.24.2″ _module_preset=”96fa8149-2d7e-4fe7-bc52-734658dc4791″ global_colors_info=”{}”]<\/p>\n The RICE model was first proposed<\/a> by Intercom Product Owner Sean McBride<\/a> in the mid-2010s.<\/p>\n The RICE model quickly gained significant popularity, and over the years, it has been simplified, supplemented, and adapted in various ways. That is why you will find quite a few different versions when searching for \u201cRICE prioritization,\u201d \u201cRICE model,\u201d or \u201cRICE method.\u201d However, the fundamental core has always remained the same \u2013 the RICE model consists of four main factors, from whose initial letters the model’s name is derived: <\/p>\n The RICE model is sensible to use only for prioritizing tasks over a longer period \u2013 1 quarter to 3 years. Prioritization with the RICE model does not replace sprint planning<\/strong> or sprint task estimations. <\/p>\n<\/blockquote>\n <\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.24.2″ _module_preset=”96fa8149-2d7e-4fe7-bc52-734658dc4791″ global_colors_info=”{}”]<\/p>\n <\/p>\n [\/et_pb_text][et_pb_image src=”https:\/\/agilecoach.ee\/wp-content\/uploads\/2024\/03\/RICE-scoring-example.png” title_text=”RICE scoring example” show_in_lightbox=”on” align=”center” _builder_version=”4.24.2″ _module_preset=”default” global_colors_info=”{}”][\/et_pb_image][et_pb_text disabled_on=”off|off|off” _builder_version=”4.24.2″ text_font=”Source Sans Pro|300|||||||” text_text_color=”rgba(0,0,0,0.89)” text_font_size=”16px” text_line_height=”1em” text_orientation=”center” custom_margin=”-1%||||false|false” custom_padding=”0px||||false|false” global_colors_info=”{}”]<\/p>\n RICE model example. Image by author. <\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.24.2″ _module_preset=”96fa8149-2d7e-4fe7-bc52-734658dc4791″ global_colors_info=”{}”]<\/p>\n Using the RICE model also helps save time spent on task analysis.<\/p>\n Ideally, the RICE score should be assigned to a task BEFORE detailing and breaking down the work (story slicing<\/em>).<\/p>\n<\/blockquote>\n If RICE scores are assigned to tasks early, we do not unnecessarily waste time analyzing tasks with too low a RICE score, as it is quite possible that this task will not be started anytime soon or it will be decided later not to do it at all.<\/p>\n [\/et_pb_text][et_pb_image src=”https:\/\/agilecoach.ee\/wp-content\/uploads\/2024\/03\/Estimations-RICE-score-and-Story-Points-scaled.jpeg” title_text=”Estimations – RICE score and Story Points” show_in_lightbox=”on” align=”center” _builder_version=”4.24.2″ _module_preset=”default” global_colors_info=”{}”][\/et_pb_image][et_pb_text disabled_on=”off|off|off” _builder_version=”4.24.2″ text_font=”Source Sans Pro|300|||||||” text_text_color=”rgba(0,0,0,0.89)” text_font_size=”16px” text_line_height=”1em” text_orientation=”center” custom_margin=”-1%||||false|false” custom_padding=”0px||||false|false” global_colors_info=”{}”]<\/p>\n Example of using the RICE model in the Scrum development framework. Image by author. <\/span><\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.24.2″ _module_preset=”96fa8149-2d7e-4fe7-bc52-734658dc4791″ global_colors_info=”{}”]<\/p>\n As mentioned earlier, the original RICE model has been adapted in various ways, and every company that wants to implement the RICE model should do the same. Here are some options you can consider when making your choice, but these are certainly not the only possibilities. <\/p>\n [\/et_pb_text][et_pb_image src=”https:\/\/agilecoach.ee\/wp-content\/uploads\/2024\/03\/icon-audience.jpeg” title_text=”icon-audience” _builder_version=”4.24.2″ _module_preset=”default” custom_margin=”|10%||10%|false|true” global_colors_info=”{}”][\/et_pb_image][et_pb_text _builder_version=”4.24.2″ _module_preset=”96fa8149-2d7e-4fe7-bc52-734658dc4791″ global_colors_info=”{}”]<\/p>\n Option A: Simple Scale<\/strong><\/p>\n Option B: Number<\/strong><\/p>\n Option C: Number + Time Period<\/strong><\/p>\n Number of customers reached within a certain period (month, quarter, year)<\/p>\n Option D: Customer Weights<\/strong><\/p>\n Weights:<\/p>\n This feature is needed by:<\/p>\n [\/et_pb_text][et_pb_image src=”https:\/\/agilecoach.ee\/wp-content\/uploads\/2024\/03\/icon-impact-150×150.png” title_text=”icon-impact” _builder_version=”4.24.2″ _module_preset=”default” custom_margin=”|10%||10%|false|true” global_colors_info=”{}”][\/et_pb_image][et_pb_text _builder_version=”4.24.2″ _module_preset=”96fa8149-2d7e-4fe7-bc52-734658dc4791″ global_colors_info=”{}”]<\/p>\n Use fixed values:<\/p>\n [\/et_pb_text][et_pb_image src=”https:\/\/agilecoach.ee\/wp-content\/uploads\/2024\/03\/icon-confidence-150×150.png” title_text=”icon-confidence” _builder_version=”4.24.2″ _module_preset=”default” custom_margin=”|10%||10%|false|true” global_colors_info=”{}”][\/et_pb_image][et_pb_text _builder_version=”4.24.2″ _module_preset=”96fa8149-2d7e-4fe7-bc52-734658dc4791″ global_colors_info=”{}”]<\/p>\n Use fixed values:<\/p>\n [\/et_pb_text][et_pb_image src=”https:\/\/agilecoach.ee\/wp-content\/uploads\/2024\/03\/icon-effort-150×150.png” title_text=”icon-effort” _builder_version=”4.24.2″ _module_preset=”default” custom_margin=”|10%||10%|false|true” global_colors_info=”{}”][\/et_pb_image][et_pb_text _builder_version=”4.24.2″ _module_preset=”96fa8149-2d7e-4fe7-bc52-734658dc4791″ global_colors_info=”{}”]<\/p>\n Option A: Simple Scale<\/strong><\/p>\n Option B: Number<\/strong><\/p>\n Number of person-months required for development, considering the entire feature lifecycle.<\/p>\n For example:<\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.24.2″ _module_preset=”96fa8149-2d7e-4fe7-bc52-734658dc4791″ global_colors_info=”{}”]<\/p>\n The RICE score calculation formula is: (Reach x Impact x Confidence) \/ Effort<\/p>\n <\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.24.2″ _module_preset=”96fa8149-2d7e-4fe7-bc52-734658dc4791″ global_colors_info=”{}”]<\/p>\n As a first step, you need to develop a RICE model that suits your organization’s needs. For this, I recommend organizing a product owner workshop<\/strong> where you can discuss the model’s factors and validate the model itself. You should allocate at least 2 hours. <\/p>\n The most challenging part is finding a suitable Reach factor. Impact and Confidence are already fixed values, so you don’t need to figure anything out yourself here. You also need to decide which is the most suitable option for the Effort factor. <\/p>\n If necessary, you can add further detail to each RICE model factor, but I recommend keeping the model simple<\/strong>. The REACH factor should consist of one, two, or at most three factors. A simple model is more challenging to develop initially, but later it is easier to remember and use. <\/p>\n Be sure to validate different model variants<\/strong> using specific development tasks. Here you can use the RICE model table template, which you can modify as needed. Analyze whether the resulting RICE scores are valid. If, for example, the REACH values are the same for all development tasks, this could be a warning sign that the inputs in their current form are not working and need further refinement, or alternatively, new and more diverse development tasks should be added for validation. <\/p>\n At the end of the workshop, write down your team’s agreement on using the RICE model<\/strong>. If you don’t reach an agreement immediately during the first workshop, don’t despair \u2013 creating a suitable RICE model is indeed a complex task. You can conduct additional analysis and then organize a follow-up workshop. <\/p>\n Regardless of which model you use, make its application consistent across all teams in your organization<\/strong>. Multiple different RICE models within the same organization can cause significant confusion. <\/p>\n<\/blockquote>\n [\/et_pb_text][et_pb_image src=”https:\/\/agilecoach.ee\/wp-content\/uploads\/2024\/03\/RICE-Prioritization-Model-Template-by-AC.png” title_text=”RICE Prioritization Model Template by AC” align=”center” _builder_version=”4.24.2″ _module_preset=”default” global_colors_info=”{}”][\/et_pb_image][et_pb_text disabled_on=”off|off|off” _builder_version=”4.24.2″ text_font=”Source Sans Pro|300|||||||” text_text_color=”rgba(0,0,0,0.89)” text_font_size=”16px” text_line_height=”1em” text_orientation=”center” custom_margin=”-1%||||false|false” custom_padding=”0px||||false|false” global_colors_info=”{}”]<\/p>\n RICE model table template. Image by author. <\/p>\n [\/et_pb_text][et_pb_text module_id=”tooriistad” _builder_version=”4.24.2″ _module_preset=”96fa8149-2d7e-4fe7-bc52-734658dc4791″ global_colors_info=”{}”]<\/p>\n Here you can download the RICE model development workshop instructions, a table for model validation and future use, and a RICE model cheat sheet.<\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.24.2″ _module_preset=”96fa8149-2d7e-4fe7-bc52-734658dc4791″ text_font=”Work Sans||||||||” text_text_color=”#FFFFFF” link_font=”Work Sans||||||||” link_text_color=”#FFFFFF” background_color=”#ed702d” custom_padding=”|||10px|false|false” global_colors_info=”{}”]<\/p>\n Download RICE Prioritization Model Workshop instructions<\/span><\/a> (pdf)<\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.24.2″ _module_preset=”96fa8149-2d7e-4fe7-bc52-734658dc4791″ text_font=”Work Sans||||||||” text_text_color=”#FFFFFF” link_font=”Work Sans||||||||” link_text_color=”#FFFFFF” background_color=”#ed702d” custom_padding=”|||10px|false|false” link_option_url_new_window=”on” global_colors_info=”{}”]<\/p>\nWhy is the RICE model useful?<\/h2>\n
\n
What is the RICE model about and when to use it?<\/h2>\n
\n
\n
RICE Prioritization Example<\/b><\/h2>\n
\n
Adapting the RICE Model<\/h2>\n
REACH – How many people does this affect?<\/h3>\n
\n
\n
\n
\n
IMPACT – How much does this affect? What is the magnitude of the impact? <\/h3>\n
\n
CONFIDENCE – How confident are you in the estimates for the previous two factors (REACH and IMPACT)?<\/h3>\n
\n
EFFORT – How much effort does this require?<\/h3>\n
\n
\n
or<\/li>\nCalculation Formula<\/h2>\n
How to start using the RICE model?<\/h2>\n
\n
Tools<\/h2>\n