vault backup: 2026-05-29 10:58:08
This commit is contained in:
@@ -12,7 +12,7 @@ because its single advantage over reference class forecasting
|
||||
is in itemized pricing,
|
||||
but this advantage is nullified
|
||||
by the known phenomenon that the precise
|
||||
selection of particular items and their quantities
|
||||
selection of particular items and their quantities
|
||||
can not be trusted to be exactly accurate
|
||||
due to uncertainty of project conditions,
|
||||
and by the observation that material pricing at the time of bid
|
||||
@@ -22,7 +22,7 @@ The inevitable retort is
|
||||
"It's an *est*imate, not an *exact*imate,"
|
||||
or some other such reductive dismissal.
|
||||
True enough, this method is _a_ way
|
||||
of getting close to the true answer of project cost and schedule,
|
||||
of _getting close_ to the true answer of project cost and schedule,
|
||||
but it's not an intuitive one.
|
||||
|
||||
For an organizational process to be economical
|
||||
|
||||
Reference in New Issue
Block a user