Skip to main content

Cost of Delay & WSJF Prioritization

Prioritize features using WSJF with Cost of Delay analysis. Enter values for instant results with step-by-step formulas.

Share this calculator

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.

Is WSJF the only prioritization method?

No. Alternatives include: ICE (Impact, Confidence, Ease), RICE (Reach, Impact, Confidence, Effort), MoSCoW (Must/Should/Could/Won't), and value vs effort matrices. WSJF excels when Cost of Delay is meaningful; simpler methods work for less critical decisions.

How do I interpret the result?

Results are displayed with a label and unit to help you understand the output. Many calculators include a short explanation or classification below the result (for example, a BMI category or risk level). Refer to the worked examples section on this page for real-world context.

Background & Theory

The Cost of Delay & WSJF Prioritization Calculator applies the following established principles and formulas. Break-even analysis identifies the sales volume at which total revenue equals total costs, producing neither profit nor loss. The formula divides total fixed costs by the contribution margin per unit, where contribution margin equals selling price minus variable cost per unit. If a software product has $50,000 in monthly fixed costs and each licence generates $20 above its variable cost, break-even requires 2,500 unit sales per month. Above that threshold, each additional unit contributes directly to profit. Gross margin expresses the percentage of revenue remaining after direct cost of goods sold: gross margin equals revenue minus COGS, divided by revenue. A SaaS company with 80 percent gross margins retains $0.80 of every revenue dollar to cover operating expenses, while a manufacturer with 30 percent gross margins faces much tighter operating leverage. Customer acquisition cost (CAC) divides total sales and marketing expenditure in a period by the number of new customers acquired in that same period. Customer lifetime value (LTV) estimates the total profit attributable to a customer relationship. The standard formula multiplies average revenue per user (ARPU) by gross margin and divides by the monthly churn rate. A business with $50 ARPU, 75 percent gross margin, and 2 percent monthly churn has an LTV of $1,875. The LTV:CAC ratio benchmarks unit economics health; a ratio above 3:1 is generally considered sustainable, while ratios below 1:1 indicate the business is acquiring customers at a loss. Burn rate measures monthly cash expenditure net of revenue. Cash runway equals current cash reserves divided by net monthly burn. A company with $1.2 million in the bank burning $100,000 per month has twelve months of runway. The Rule of 40 is a benchmark for SaaS health: the sum of annual revenue growth rate (as a percentage) and profit margin (as a percentage) should equal or exceed 40. High-growth companies burning cash can still pass this rule if their growth rate compensates.

History

The history behind the Cost of Delay & WSJF Prioritization Calculator traces back through the following developments. Early economic thought centred on mercantilism, the 16th and 17th century doctrine that national wealth derived from accumulating precious metals through export surpluses and colonial extraction. Adam Smith's "Wealth of Nations" in 1776 dismantled this framework, arguing that genuine prosperity arose from specialisation, division of labour, and freely operating markets. David Ricardo extended Smith's work with the theory of comparative advantage in 1817, demonstrating mathematically that mutually beneficial trade was possible even when one country was less productive in every industry. Alfred Marshall's "Principles of Economics" published in 1890 provided the modern framework of supply and demand curves, consumer surplus, price elasticity, and marginal analysis, establishing neoclassical economics as the dominant academic paradigm for decades. The Great Depression exposed the limits of laissez-faire assumptions, and John Maynard Keynes's "General Theory of Employment, Interest and Money" in 1936 argued that private-sector aggregate demand failures required countercyclical government fiscal intervention to restore full employment, shifting the policy consensus toward active macroeconomic management. The post-World War II decades constructed mixed-economy models combining market allocation with expanded welfare states and Keynesian demand management. Milton Friedman and the Chicago School challenged this consensus from the 1960s onward, championing monetarism and arguing that stable money supply growth was superior to discretionary fiscal policy. Their influence shaped the deregulatory and privatisation policies of the Reagan and Thatcher eras in the 1980s. Behavioural economics emerged through the work of Daniel Kahneman and Amos Tversky in the 1970s and Richard Thaler in the 1980s, using psychology to demonstrate that real human decision-making deviates systematically from rational-actor models through heuristics and biases. The rise of the internet and mobile platforms in the 2000s and 2010s created a new category of platform economics, where network effects, near-zero marginal cost of digital goods, and two-sided market dynamics generated winner-take-most competitive outcomes requiring new analytical frameworks for business valuation.

References