Adding my two cents to Gerard's comments, I think it is also related to the
estimation process itself. If I have 2 painters available and need to paint
a wall, how do I know how long it will take them? Probably I'm going to
look back at similar tasks in other projects and see how long they took.
Perhaps in the last 5 projects we did, a similarly sized wall took a crew of
two 4 days to complete. But does that really tell me how many actual
man-hours was REALLY required? No, 'cause I don't know how much of that 4
days was spent actively applying paint versus hours spent drinking coffee,
going to the bathroom, talking sports, etc. All I really know with any
reliability it is usually takes a crew of 2 painters XX hours total duration
to paint a wall of YY square feet - the minute-by-minute details of what is
happening during that time are forever lost. So I enter duration, assign
the resources, and let Project calculate the man-hours based on my
assignments so that it can have something to work with for cost estimates
and schedule recalculation when I subsequently edit the assignments. In
terms of scheduling and hitting delivery dates, the work estimates are
really secondary to duration estimates. Frankly I've always found it a
mystery how anyone can say "We're going to allow for YY man-hours to
complete this thing" anyway. It always seems like a bit of hocus-pocus is
involved along with a belief that the work required is somehow something
that can be set by declaration. IMHO, you discover the budget that is
implicit within a deliverable and don't adjust the deliverable to fit a
preconceived notion of what the budget 'ought' to be.
--
Steve House [Project MVP]
MS Project Trainer & Consultant
Visit
http://www.mvps.org/project/faqs.htm for the FAQs
Samantha Gore said:
Hi Gerard, thankyou for the reply.
With regard to my first question, I didn't put it clearly enough. I know
how
to insert the column but am intrigued as to why Mircrosoft have never made
it
a standard column in the table.
For the second one, I am wrestling with the age old problem of planning
one
set of dates for my developers to work to, and presenting another set to
my
Director/ customer with contingency in without it being apparent and the
customer stripping out the reality from the project. Increasingly I think
PERT is the way to do it but need to play a bit more with how MSP works,
and
especially what is the impact on 'Work' since the PERT calculations all
seem
to operate on the 'Duration' fields.
Regards, Samantha