WSJF (Weighted Shortest Job First) Template

[RICE](/frameworks/rice-framework) scores features on Reach, Impact, Confidence, and Effort. WSJF scores on Cost of Delay (three sub-components) divided by Job Duration. The key difference is WSJF explicitly captures time sensitivity. A feature with a hard deadline in 4 weeks scores higher in WSJF than one with the same value but no deadline. RICE does not account for this.

If nothing is time-sensitive, the Time Criticality scores will be similar and WSJF reduces to (User-Business Value + RR/OE) / Job Duration. In that case, WSJF still works but you get less differentiation from it. Consider using RICE or ICE instead if time sensitivity is not a major factor in your backlog.

WSJF works best at the epic or feature level. User stories are too granular for meaningful Cost of Delay estimates. Score features and epics with WSJF to determine build order, then break them into stories and use story points or t-shirt sizing for sprint-level planning.

Use relative sizing. Pick the smallest feature as your baseline (score 1) and rate everything else relative to it. A feature that is roughly 3x the effort gets a 3. One that is 8x gets an 8. You do not need precise hour estimates. Relative sizing is sufficient for sequencing decisions.

Yes. The three standard components (User-Business Value, Time Criticality, RR/OE) work for most teams. If your context requires it, you can add a fourth component (for example, Regulatory Urgency) or replace RR/OE with a domain-specific dimension. Just keep the total number of components at 3-4 to avoid scoring fatigue.