Why start CoD component estimates with a baseline value of 1?

Why start CoD component estimates with a baseline value of 1?

• A. To reflect absolute cost
• B. To expedite decision making by skipping discussion
• C. To anchor estimates and enable relative sizing
• D. To confuse team members

Answer: (C)

In WSJF, the Cost of Delay components are tied to a common reference unit so you can compare items quickly and fairly. Starting each CoD component at a baseline of 1 anchors the scale, making the numbers purely relative rather than tied to absolute dollars or hours. When you rate components like business value, time criticality, and risk reduction, a score of 3 means three times the baseline value, and you get a simple sum for the CoD (for example, 3 + 2 + 1 = 6). This keeps the Cost of Delay a clear, interpretable relative measure that, when divided by the job size, yields a consistent, comparable WSJF value across backlog items. It also prevents zeros and keeps the math straightforward, which supports consistent decision-making.

In WSJF, the Cost of Delay components are tied to a common reference unit so you can compare items quickly and fairly. Starting each CoD component at a baseline of 1 anchors the scale, making the numbers purely relative rather than tied to absolute dollars or hours. When you rate components like business value, time criticality, and risk reduction, a score of 3 means three times the baseline value, and you get a simple sum for the CoD (for example, 3 + 2 + 1 = 6). This keeps the Cost of Delay a clear, interpretable relative measure that, when divided by the job size, yields a consistent, comparable WSJF value across backlog items. It also prevents zeros and keeps the math straightforward, which supports consistent decision-making.