Of course if you use elapsed time it implies work proceeds 24/7 and no one
ever gets any time off, not even a meal break. Machines work like that but
people don't.
You stated ealier that Project's normal definition of duration doesn't work
to plan the project. Of course it does, in fact it's about the only
reliable way to come up with a schedule that can successfully predict the
outcomes of the management decisions you make. You need to schedule all the
activities that need to take place to bring your new product online. But as
I said before, activities only take place when the people responsible for
them are physically present and working. Planning your project around their
scheduled working time is the only way an activity schedule makes sense. If
activity X takes 3 days of work and it starts on Monday, it will finish Wed,
3 workdays later. But if it starts on Friday, it will finish Tue, 5 elapsed
days but still 3 workdays, later. Using elapsed days will give a schedule
that is a highly inaccurate representation of what is actually physically
possible.
--
Steve House [Project MVP]
MS Project Trainer & Consultant
Visit
http://project.mvps.org/faqs.htm for the FAQs
It may be helpful to you to know that you can use the concept of
'elapsed' time in Project. So if you enter a duration of 1 emo it will
be one elapsed month rather than 1 working month. Of course,the length
of the elapsed month will depend on how may days you have set a month to
be which is not the same month to month.
- Show quoted text -
Thanks - that is interesting, didn't know about that one.