Cost of Delay & WSJF Prioritization
Prioritize features using WSJF with Cost of Delay analysis. Enter values for instant results with step-by-step formulas.
Worked Examples
Example 1: Product Backlog Prioritization
Problem:A product team has four features to prioritize: New Dashboard (high value, medium effort), Security Patch (medium value, urgent, small), API Refactor (enables future work, large), Mobile App (high value, large). Apply WSJF.
Solution:WSJF Scoring (1-10 scales):\n\n1. New Dashboard\n - User Value: 8\n - Time Criticality: 4 (no deadline)\n - Risk Reduction: 3\n - CoD = 8 + 4 + 3 = 15\n - Job Size: 5\n - WSJF = 15/5 = 3.0\n\n2. Security Patch\n - User Value: 5 (compliance)\n - Time Criticality: 9 (regulatory deadline)\n - Risk Reduction: 8 (reduces breach risk)\n - CoD = 5 + 9 + 8 = 22\n - Job Size: 2\n - WSJF = 22/2 = 11.0 ⭐ HIGHEST\n\n3. API Refactor\n - User Value: 4 (indirect)\n - Time Criticality: 3\n - Risk Reduction: 7 (enables 3 future features)\n - CoD = 4 + 3 + 7 = 14\n - Job Size: 8\n - WSJF = 14/8 = 1.75\n\n4. Mobile App\n - User Value: 9\n - Time Criticality: 5\n - Risk Reduction: 4\n - CoD = 9 + 5 + 4 = 18\n - Job Size: 8\n - WSJF = 18/8 = 2.25\n\nPriority Orde
Result:Security Patch first (WSJF 11.0) despite lower user value - urgency and small size make it highest priority
Example 2: Quarterly Planning with Dependencies
Problem:Platform team must prioritize: Kubernetes Migration (enables team velocity), New Auth System (security requirement), Performance Optimization (user complaints), Analytics Pipeline (business intelligence need). Q3 has 13 weeks capacity.
Solution:WSJF Analysis with Dependencies:\n\n1. Kubernetes Migration\n - User Value: 3 (indirect)\n - Time Criticality: 6 (blocks other work)\n - Risk Reduction: 5 (reduces incidents)\n - CoD = 14\n - Job Size: 5 weeks\n - WSJF = 14/5 = 2.8\n - Note: Enables Performance Optimization\n\n2. New Auth System\n - User Value: 4\n - Time Criticality: 8 (compliance by Q4)\n - Risk Reduction: 9\n - CoD = 21\n - Job Size: 4 weeks\n - WSJF = 21/4 = 5.25 ⭐ HIGHEST\n\n3. Performance Optimization\n - User Value: 7 (customer complaints)\n - Time Criticality: 5\n - Risk Reduction: 3\n - CoD = 15\n - Job Size: 3 weeks (requires K8s)\n - WSJF = 15/3 = 5.0\n - Dependency: Kubernetes Migration\n\n4. Analytics Pipeline\n - User Value: 6\n - Time Criticality: 4\n - Risk Redu
Result:Auth → Kubernetes → Performance | Analytics deferred | Respects dependencies while maximizing WSJF
Example 3: Startup Feature Prioritization Under Constraints
Problem:Early-stage startup with 2 engineers must choose between: Core Feature Enhancement (existing users want), New Market Feature (opens new segment), Technical Debt (slowing development), Partnership Integration (large customer request, deadline).
Solution:Startup Context WSJF:\n\n1. Core Feature Enhancement\n - User Value: 7 (retention)\n - Time Criticality: 5\n - Risk Reduction: 4 (reduces churn)\n - CoD = 16\n - Job Size: 3 weeks\n - WSJF = 16/3 = 5.3\n\n2. New Market Feature\n - User Value: 8 (growth)\n - Time Criticality: 6 (competitor entering)\n - Risk Reduction: 2\n - CoD = 16\n - Job Size: 6 weeks\n - WSJF = 16/6 = 2.7\n\n3. Technical Debt\n - User Value: 2 (indirect)\n - Time Criticality: 3\n - Risk Reduction: 6 (dev velocity)\n - CoD = 11\n - Job Size: 4 weeks\n - WSJF = 11/4 = 2.75\n\n4. Partnership Integration\n - User Value: 6 ($50K ARR customer)\n - Time Criticality: 9 (hard deadline in 5 weeks)\n - Risk Reduction: 5 (validates enterprise market)\n - CoD = 20\n - Job Size: 2 weeks\
Result:Partnership (WSJF 10.0) → Core (5.3) → Market (2.7) | Tech debt via continuous improvement
Frequently Asked Questions
What is WSJF (Weighted Shortest Job First)?
WSJF is a prioritization framework from SAFe (Scaled Agile Framework) that divides Cost of Delay by job size. It ensures you tackle work that delivers the most value per unit of time invested, maximizing economic outcomes across your backlog.
What is Cost of Delay?
Cost of Delay quantifies the economic impact of not delivering something sooner. It combines user/business value, time criticality (urgency/deadlines), and risk reduction/opportunity enablement. Higher CoD means delaying hurts more.
What are common WSJF pitfalls?
Common mistakes: gaming scores to favor pet projects, inconsistent scale interpretation across teams, ignoring dependencies, not re-evaluating as context changes, and treating scores as absolute truth rather than decision inputs.
How often should I recalculate WSJF?
Recalculate when: new information changes estimates, priorities shift, market conditions change, or items age (time criticality may increase). At minimum, review quarterly. For fast-moving contexts, review monthly or per sprint.