It occurs because durations are stored and tracked to the nearest minute,
regardless of the units you display duration in. What would you suggest the
project should show as the number of days of duration if the duration for a
task turns out to be, say, 20 hours? There is no integer multiple of an 8
hours workday that is precisely 20 hours. Or you have a task that you say
will have a two day duration and you assign Mary to it 100%. Now Mary's
boss calls you and say she needs her a couple of hours a day on something
else. So you reduce Mary from 100% to 75% (6 hours a day). But she still
has to do 16 man-hours of work on the task in your project, that's what it
means when you assigned her to a two day task 100% - that task is expected
to take man-hours 16 hours of work to complete, no more and no less. So
she's working 6 hours per day, not 8, which means it will take her 2.5 days
of duration to work that required 16 man-hours. Hence decimal durations.
While you can fudge it with rounding or truncation, that is a dangerous
practice because it introduces errors in the project schedule that are
cummulative and can result in a schedule that is considerably off the mark
over the course of a longish project. You can have simplicity or you can
have accuracy, but never count on having both at once.
--
Steve House [MVP]
MS Project Trainer/Consultant
Visit
http://www.mvps.org/project/faqs.htm for the FAQs
ruth said:
hi, please can i know how i can change my total durations from decimal (ie
55.11days) days to whole number days.why does that occur anyway?