Prioritization Calculator

Free RICE, WSJF, MoSCoW, and ICE calculators in one place. Rank your backlog in 30 seconds.

The Prioritization Calculator supports four PM frameworks โ€” RICE, WSJF, MoSCoW, and ICE โ€” in one unified interface. Free, no signup, exports to CSV and Markdown. Hand-verified formulas matching each framework's authoritative source (Intercom for RICE, SAFe for WSJF).

MoSCoW Classification

MoSCoW classifies items into four buckets: Must have (critical), Should have (important but not vital), Could have (nice to have), Won't have (explicitly out of scope). Simple, fast, and excellent for MVP scoping.

ItemClassificationNotes

How each framework works

RICE (Reach ร— Impact ร— Confidence รท Effort)

Origin: Developed by Intercom in 2016.

  1. Estimate reach: How many people does this feature affect per quarter? Use specific numbers from analytics.
  2. Score impact: Rate impact on a scale: 3 = massive, 2 = high, 1 = medium, 0.5 = low, 0.25 = minimal.
  3. Assign confidence: As a percentage: 100% = high confidence with data, 80% = medium, 50% = low (gut feel).
  4. Estimate effort: In person-months. Include design + engineering + QA. Be honest about scope creep.
  5. Calculate and rank: Score = (Reach ร— Impact ร— Confidence%) รท Effort. Sort descending. The top item ships first.
WSJF (Weighted Shortest Job First)

Origin: Part of SAFe (Scaled Agile Framework).

  1. Score business value (1-10): How much revenue or user value does this create?
  2. Score time criticality (1-10): Does value decay over time? Is there a deadline or competitive pressure?
  3. Score risk reduction (1-10): Does this de-risk something? Unblock a dependency? Enable future work?
  4. Score job size (1-10): Inverse of effort. 10 = tiny, 1 = huge.
  5. Calculate WSJF: WSJF = (Business Value + Time Criticality + Risk Reduction) รท Job Size. Highest WSJF ships first.
MoSCoW (Must / Should / Could / Won't)

Origin: DSDM framework, 1994.

  1. Classify each item: Drop each requirement into exactly one bucket: Must, Should, Could, or Won't.
  2. Validate balance: Aim for 60% Must-haves, 20% Should-haves, 20% Could-haves. If 90% are "Must" you're not being honest.
  3. Confirm "Won't": Explicit exclusions kill scope creep. Always have "Won't" items.
  4. Ship Musts first, Shoulds next: Musts are non-negotiable. Shoulds get into this release if time permits. Coulds are stretch.
ICE (Impact ร— Confidence ร— Ease)

Origin: Popularized by Sean Ellis and growth hackers.

  1. Score impact (1-10): If this works, how big is the win?
  2. Score confidence (1-10): How sure are you it will work? Do you have data?
  3. Score ease (1-10): How fast and cheap is it? 10 = trivial, 1 = massive undertaking.
  4. Calculate ICE: ICE = Impact ร— Confidence ร— Ease. Rank descending. Top-scoring items ship this week.

Frequently Asked Questions

What's the difference between RICE and ICE?

RICE has a Reach dimension and Effort; ICE has neither โ€” it uses Ease (inverse of effort). RICE is better for product roadmap prioritization; ICE is faster for growth experiments.

When should I use WSJF?

WSJF is designed for scaled agile (SAFe) environments where multiple teams share a backlog. If you're a single squad, RICE is simpler.

Can I save my work?

Yes โ€” the "Copy Share Link" button encodes all your items into a URL that you can save or share. No server-side storage.