31 lines
909 B
Markdown
31 lines
909 B
Markdown
# EVPI Takeoff
|
|
|
|
Expected value of perfect information (EVPI)
|
|
|
|
The perceived *value* of decreased uncertainty
|
|
must be weighed against its *cost*.
|
|
|
|
Takeoff purchases certainty with estimator hours.
|
|
Estimator hours have a not insubstantial real cost in salary and burden,
|
|
however the opportunity cost may exceed this.
|
|
|
|
Count-based takeoff speed increases with count.
|
|
|
|
***
|
|
|
|
Optimizing the takeoff process means:
|
|
|
|
* *Minimizing* the need for information outside of drawings
|
|
* *Maximizing* organizational consistency
|
|
|
|
***
|
|
|
|
Recent events have complicated my philosophy above.
|
|
It appears that similar efforts have already been made here,
|
|
their success being a matter of perspective.
|
|
|
|
## Naming Conventions (Use Case vs. Description)
|
|
|
|
Naming by use case is intuitive for those without estimating or field experience,
|
|
but has the side effect that those acustomed to the names will inevitably treat them as descriptive.
|