It is a muddle all right. Project makes the distinction between "%
Complete", "% Work Complete", and "% Physical Complete." On top of that, if
I show that the 5-day task is 80% complete, it shows progress complete
through day 4 and Work as complete that was scheduled for days 1, 2, 3, and
4 whether or not that is the same percentage of work. But I can break that
link in the options page and post duration and work progress completely
independently of each other. Then to top it off, one can choose to use %
Complete or % Physical Complete for the Earned Value calculations.
One of the major issues that I think PM's need to keep in mind is when you
go to the resource working on a task and ask him "How's it going?" and he
responds "We're halfway done" what does he really mean? Is he referring to
the time he's spent so far compared to the total time it's expected to take,
is it the man-hours of work that have been put in compared to the total
man-hours required (quite different from duration time requirements but a
distinction that is almost always overlooked by resources, as well as too
often overlooked by PM's), or the actual physical progress on the
deliverable? And if we say the deliverable is 50% complete, just what do we
mean. If we have to lay a wall requiring 100 bricks and we've put 50 in
place it's pretty straight forward but what does "50% Physical Complete"
really mean when designing an engine or writing a program?
There are three common ways of estimating the percentage progress:
1: Tasks that are complete are rated 100%, tasks not started or
in-progress are rated 0%.
2: Tasks that are complete are rated 100%, tasks in-progress are rated
50%, tasks unstarted are 0%.
3: Tasks are rated with an estimated completion reflecting the actual
(perceived) percentage progress.
The last method is particulary loosey goosey if one tries to approach it by
entering percentages. A far better way, if one needs that level of
precision (and I really have my doubts how often it is really needed - what
data actually helps you manage the project and a bunch of numbers that look
impressive in a presentation by your boss to the board of directors are
often two entirely different critters) is to forget estimating percentages
altogether and instead ask the resources "How much have you done" and "When
do you think it'll be finished, ie, Actual Duration and a revised estimate
of Remaining Duration, and let Project massage that into a percentage. "We
worked on it all 5 days this week and if we can continue on it every day, it
looks like it'll be another 2 weeks before it's finished" translates into
33% done, regardless of what the original estimated duration was or what the
anticipated work contours might be.
--
Steve House [MVP]
MS Project Trainer/Consultant
Visit
http://www.mvps.org/project/faqs.htm for the FAQs