Prioritize backlog items using relative cost of delay and size without pretending the numbers are exact.
Four candidate items compete for two delivery slots: consent logging, demo polish, billing refactor, and dashboard export. Lightweight WSJF: compare cost of delay against job size to make priority reasoning visible. The trap is scoring to justify a pre-decided favorite, or adding decimals that imply accuracy the team does not have. Name delay components For each item, discuss business value, deadline/time criticality, and risk reduction. Cost of delay should be grounded in consequences, not stakeholder volume. Use relative size Estimate size as small, medium, large or 1, 3, 8, 13. Apply it to the actual agile work item so the…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in