Feature Prioritization Calculator (RICE, ICE, WSJF, MoSCoW, Kano)

About the Feature Prioritization Calculator (RICE, ICE, WSJF, MoSCoW, Kano)

Put a backlog in order with the method your team uses. RICE scores an item by Reach × Impact × Confidence ÷ Effort, ICE by Impact × Confidence × Ease, WSJF by its cost of delay — user-business value plus time criticality plus risk reduction or opportunity enablement — divided by its job size, value vs effort by value ÷ effort with the 2 × 2 of quick wins, big bets, fill-ins and time sinks, and MoSCoW sorts it into Must have, Should have, Could have and Won’t have this time. The Kano mode reads a survey of functional and dysfunctional answers and puts each feature in a category with its better and worse coefficients.

Type the items, paste a range from a spreadsheet, or open the CSV or Excel export of your issue tracker or kanban board. The ranking shows the working of every score, the quadrant of each item on the 2 × 2, and how far one estimate would have to move before the item changes place — so you can see which positions are firm and which hang on a guess.

Without a pass the ranking is a free preview: the top-ranked item, the first rows of the ranking (up to 3), the rule and the first step of the working, and the chart as a watermarked picture. A Pro pass shows the whole ranking with its sensitivity and the Kano analysis, and unlocks the CSV to import back into your tracker, the chart as PNG and a one-page PDF for stakeholders.

Common uses

• A product manager ranking next quarter’s feature requests before a planning meeting.
• A SAFe team sequencing features for a Program Increment with WSJF.
• A start-up founder deciding which ideas are quick wins and which are big bets.
• A researcher turning a Kano survey into the must-be, performance and attractive features of a product.

The formulas and where they come from

• RICE (Intercom’s RICE article): Reach × Impact × Confidence ÷ Effort. Reach is people or events in a period, impact 3 massive, 2 high, 1 medium, 0.5 low and 0.25 minimal, confidence 100% high, 80% medium and 50% low, effort in person-months.
• WSJF (SAFe: WSJF): the relative cost of delay divided by the relative job duration, where the cost of delay adds user and business value, time criticality, and risk reduction and/or opportunity enablement. SAFe estimates on the modified Fibonacci sequence 1, 2, 3, 5, 8, 13, 20, 40, 100 (SAFe glossary); switch to any numbers under Scales and weights.
• MoSCoW (Agile Business Consortium): Must Have, Should Have, Could Have and Won’t Have this time. Its guidance keeps typically no more than 60% of the effort Must Have and around 20% Could Have, the work dropped first when time runs short; the page checks your split when the items have an effort.
• ICE: Impact × Confidence × Ease, each scored 1 to 10 (or averaged, if your team averages them).
• Value vs effort: value ÷ effort, each 1 to 10, with the lines of the 2 × 2 where you set them.

How firm is each place?

For every ranked item the page works out, one estimate at a time with the others unchanged, the smallest change that lifts it above the item before it or drops it below the item after it — for example “+12% Reach (2,000 → 2,240) passes Bulk import”. Estimates on a scale (RICE impact, 1–10 scores, Fibonacci sizes) move in whole steps; the others by any amount within their range (confidence at most 100%). An item is flagged when that change is within the threshold you choose (5% to 33%) or when it ties with another item. A flagged item is not wrong — its place depends on how good one estimate is, so check that estimate before you commit to the order.

Importing from a tracker or a board

The first row of the file names the columns. The page matches the usual names — Summary or Title, Issue key or ID, Reach, Impact, Confidence, Effort or Story Points, Business Value, Time Criticality, Job Size, Priority or Labels for MoSCoW — and you can change each match before adding the rows. Numbers may be written 1,200 or 1.200,5, percentages with %, RICE impact as its word (High), and MoSCoW buckets as words or letters (Must have, S). Rows without a title are left out and counted. The CSV export keeps the item’s key in the column name your tracker used and adds the priority score and rank, ready for the tracker’s own CSV import to update the same items.

The Kano survey

Each respondent answers two questions per feature: how they would feel if the product had it (functional) and if it did not (dysfunctional), each with “I like it”, “I expect it”, “I am neutral”, “I can tolerate it” or “I dislike it”. The pair gives a category from the Kano evaluation table: attractive, performance (one-dimensional), must-be, indifferent, reverse or questionable (a guide to the Kano model). A feature takes its most frequent category, ties going must-be, performance, attractive, indifferent, and the list is ordered that way. Better = (A + O) ÷ (A + O + M + I) and worse = −(O + M) ÷ (A + O + M + I) (the satisfaction coefficients); the chart puts each feature by both. The stricter table, which also counts “I expect it” or “I can tolerate it” given to both questions as questionable, is an option.

Limitations

• The scores are only as good as the estimates: the page shows how much they matter, not whether they are right.
• One backlog at a time is kept in this browser; save it as a JSON file to keep several or to move it to another device.
• The backlog holds up to 500 items, and a survey up to 80 features and 20,000 respondents.
• Writing the scores back into a tracker uses that tracker’s own CSV import; nothing is sent to it from here.

Privacy

On this device; its files download once

Everything happens in your browser. The backlog and its settings are kept in this browser on this device so they are there when you come back; a survey file is read on the page and not kept. Nothing you type, open or paste is uploaded.