Well, it can be used for schedule management but isn't much use for
budget
management. I can't believe how many PM's say, to effect, "We don't care
how much our project costs." Makes one wonder at the reason their firms
are
even in business (and doesn't bode well for the long term viability of
the
firm).
--
Steve House [MVP]
MS Project Trainer & Consultant
Visit
http://www.mvps.org/project/faqs.htm for the FAQs
Whenever they plot the Hours S Curve and track Hours instead of Costs,
this effectively is an assumption that all Hours have the same Cost, eg
$1/hour will do, as you say.
Hours become a proxy currency.
But it sucks, doncha think?
It is such a distortion of the reality as to be meaningless.
It is not so bad if it is just a plot of Cumulative Hours but the uses
to
which it is put creates the real problem.
Mainly, it is sometimes used as a way of measuring progress, ie actual
cumulative hours compared to planned cumulative hours.
Sometimes, I have seen an idea which is "Earned Hours". That is, each
completed part of any Task is a percentage of progress for that Task eg
50%. Then each Task has "earned" hours = 50% of the
budget/planned/baseline/estimated Hours.
Then cumulative "earned" hours compared to planned cumulative hours
and
if less then behind progress, throw in more troops, "earn more hours".
I just think this is erzatz earned value, very misleading, too simple,
mis-interpreted, over-rated.
Thanks
"Steve House [Project MVP]" <
[email protected]>
wrote in message Days of duration won't do it for an "S" curve but man-hours of work
scheduled versus completed will. Since you're not tracking costs,
arbitrarily assign a standard rate of $1.00 to each resource. On the
Tools, Options menu, View page set the units of currency to a blank.
Now
your EV reports will report numbers of man-hours rather than dollars.