Cost of Delay Results

❕ For the results to be valid, the unit of time measure should all be consistent and the cost of delay normalized to that time frame. For example, all values in the column should be "7 days" or "30 days".

Feature

Cost of delay

per (unit of time)

Duration of effort

CD3 Score

Digital kanban simulation

$500

Per week

60 days

8.3

Stand-up check in

Per week

Guide to asyncronous work

Team aligment snapshot

Cultural assessment quiz

Easy team metrics

Project brief

There are no rows in this table

⁠

About CD3 Score

CD3 is an abbreviation of "Cost of Delay Divided by Duration"

⁠

When we have a collection of potential feature and their CD3 scores, the CD3 score tells us know which option should be delivered first. It does this by considering which feature incurs the largest cost of delay (the cost we incur as long as the feature is not available) compared to how quickly it could be delivered.

About Cost of Delay

The first thing you may have noticed is that entering data for Cost of Delay asked a lot more questions about your features. The reason for this is that a lot of discussions around value include assumptions. The questions help individuals and groups come to a clearer common understand of a feature, and a better understanding of the value of doing it.

Another change is switching from the looking at the value a feature provides, and instead the value that is lost by not having a feature.

This more advanced technique is not to be used in all situations. If you can make a good enough prioritization decision without discovering the cost of delay and CD3 score for every feature, you should do it. Use cost of delay between a small set of items, or when the stakes are high, to get very precise guidance on sequencing features.

⁠

Cost of Delay & CD3 Links

⁠

Loading…⁠

⁠

Loading…⁠

⁠

Gallery

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.