WSJF Prioritization
Framework Template

Score every Feature, Capability, or Epic by Cost of Delay divided by Job Size — then sequence work for maximum economic benefit, not maximum noise.

Use Template

Four inputs. One score.

WSJF turns sequencing into a calculation. Every Feature, Capability, or Epic gets scored on Cost of Delay and Job Size, so the shortest job with the highest cost of waiting moves first — not whichever team argues loudest. Read how to customize WSJF for your business goals .

User-Business Value

How much relative value does this deliver to the customer or the business?
Scored with the modified Fibonacci scale: 1, 2, 3, 5, 8, 13, 21 — relative to the other jobs in the backlog.

Time Criticality

How much does the value decay if this waits?
Scored the same way — a fixed launch date or compliance deadline scores high, work that's just as valuable in six months scores low.

Risk Reduction / Opportunity Enablement

Does this reduce risk or unlock a future opportunity?
Scored on the same scale — a spike that de-risks next quarter's roadmap can score high with no direct user value.

Job Size

How much work will this take, relative to other jobs in the backlog?
Scored as a relative estimate on the same Fibonacci scale as Cost of Delay — not a time unit.

// the formula

WSJF = Cost of Delay ÷ Job Size

Cost of Delay sums three inputs — User-Business Value, Time Criticality, and Risk Reduction/Opportunity Enablement — then divides by Job Size, so a small job with a high cost of waiting always outranks a big job with a low one.

Ducalis computes the score live as your team fills in each field, no spreadsheet required.

┌─ WSJF SCORE · CALCULATOR ────────────────────────┐
│                                                  │
│  User-Business Value                          8  │
│  Time Criticality                            13  │
│  RR-OE Value                                  5  │
├──────────────────────────────────────────────────┤
│  Cost of Delay                               26  │
│  Job Size                                     5  │
│                                                  │
│  WSJF = 26 / 5 = 5.2                             │
└──────────────────────────────────────────────────┘
// sequenced output

Every Feature, Capability, or Epic, sequenced by the same math

Once every job carries a WSJF score, the sequence sorts itself — the job that's most expensive to delay, relative to its size, moves to the front of the queue.

Learn how scores sync back to your task tracker.

┌─ BACKLOG · SEQUENCED BY WSJF ────────────────────┐
│  API rate limit increase               5.2 · #1  │
│  Onboarding email flow                 3.3 · #2  │
│  Design system dark mode               0.5 · #3  │
│                                                  │
│  ▸ re-sequences live as inputs change            │
└──────────────────────────────────────────────────┘

Example: sequencing a real backlog

Three jobs, three Cost of Delay inputs plus Job Size, one sequenced list — this is what a WSJF-scored backlog looks like in practice.

Feature / Capability UBV Time Crit. RR-OE Cost of Delay Job Size WSJF Rank
API rate limit increase 8 13 5 26 5 5.2 #1
Onboarding email flow 5 3 2 10 3 3.3 #2
Design system dark mode 2 1 1 4 8 0.5 #3
// native scoring

Score with WSJF natively in Ducalis

WSJF is a built-in framework — no setup, no custom fields to wire up. Open a board, pick WSJF, and start scoring.

Prefer RICE, ICE, MoSCoW, Eisenhower Matrix, or your own criteria? Switch frameworks anytime — the same backlog carries over.

┌─ SCORE THIS FEATURE ─────────────────────────────┐
│  User-Business Value                    [  8  ]  │
│  Time Criticality                       [ 13  ]  │
│  RR-OE Value                            [  5  ]  │
│  Job Size                               [  5  ]  │
│                                                  │
│  ▸ WSJF  5.2 · auto-computed                     │
└──────────────────────────────────────────────────┘

Where teams use WSJF

WSJF fits anywhere SAFe teams sequence Features, Capabilities, or Epics — here's where it shows up most.

┌─ PI PLANNING ──────────────────────────────┐
│  FEATURE QUEUE · SEQUENCED                 │
│                                            │
│  Checkout latency fix            WSJF 8.4  │
│  New reporting API               WSJF 4.1  │
│                                            │
│  ▸ top of queue = Sprint 1                 │
└────────────────────────────────────────────┘
PI Planning
Walk into Program Increment Planning with Features already sequenced by WSJF, so the room debates dependencies — not which Feature goes first.
┌─ PORTFOLIO KANBAN ─────────────────────────┐
│  Analysis                         6 epics  │
│  Implementing                     3 epics  │
│                                            │
│  Highest WSJF epic pulled next             │
└────────────────────────────────────────────┘
Portfolio Kanban
Rank Epics waiting to enter Implementation so the ones with the highest cost of delay move through the funnel first.
┌─ DEPENDENCY QUEUE ─────────────────────────┐
│  Auth-service migration                    │
│  Blocks                3 downstream teams  │
│  Job Size                               8  │
│                                            │
│  ▸ WSJF surfaces the blocker               │
└────────────────────────────────────────────┘
Dependency Sequencing
When one team's small job blocks three others downstream, WSJF surfaces it — Time Criticality alone won't.
┌─ IDEA #42 → WSJF 5.2 ──────────────────────┐
│  Add SSO for enterprise plans              │
│  Upvotes                               96  │
│                                            │
│  ▸ scored, sequenced, ready                │
└────────────────────────────────────────────┘
Feedback Linking
Customer upvotes and support-ticket volume feed straight into Time Criticality, so urgent requests naturally sequence higher.

Ducalis—The Decision-Making Toolkit

Ducalis helps companies capture user requests, estimate job size, and sequence the backlog with WSJF — or any framework your team prefers.
No credit card required. Unlimited users. No time limit.

┌─────────────────────────┐
│  COST OF DELAY          │
│  ÷ JOB SIZE             │
│  = WSJF                 │
└─────────────────────────┘