vault backup: 2025-07-03 17:48:00
This commit is contained in:
@@ -0,0 +1,30 @@
|
||||
# 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.
|
||||
Reference in New Issue
Block a user