Which approach is recommended for estimating CoD components?

• A. Estimate individually by product owner only
• B. Involve the team, use modified Fibonacci, start with 1 in the column
• C. Use velocity to determine CoD values
• D. Use fixed, pre-defined values regardless of team input

Answer: (B)

Cost of Delay components are estimated through a team-based, relative scoring process as part of WSJF. The recommended approach is for the cross-functional team to estimate User/Business Value, Time Criticality, and Risk Reduction/Opportunity Enablement using planning poker with a modified Fibonacci scale, starting with 1 in the column. This gives a consistent reference point and supports comparing items by how much value they delay, while naturally handling uncertainty as numbers grow in a non-linear way. Involving the whole team brings multiple perspectives—business context, architecture, and development—leading to broader buy-in and more accurate WSJF rankings. Using velocity to set CoD values would tie value to delivery pace rather than impact, and fixed predefined values ignore context and team input, making the estimates brittle.