Summary Task non-whole durations

[Steve Scott]

If I have a Summary task showing eg 42.3 days total duration. I want to
understand all possible reasons for the decimal part of the value. I belive
they could be:-

1) Non-whole lag and lead times

2) Task durations eg 3hrs out of a 8 hr day

Are there any other reasons that could cause this?

 

[JackD]

Partial days, odd calendars or wierd lags would all be reasons. Take a look
at things like actual duration and remaining duration to see if there are
partial days involved.

 

[Mike Glen]

Hi Steve,

Welcome to this Microsoft Project newsgroup

See also FAQ Item: 5. Default Working Hours

FAQs, companion products and other useful Project information can be seen at
this web address: http://www.mvps.org/project/

Hope this helps - please let us know how you get on

Mike Glen
Project MVP

 

[Steve House [Project MVP]]

To determine why a given summary task has a fractional day duration you have
to analyze what's going on with its subtasks and every case might be
different. The duration of a summary task is the amount of calendar working
time between when its earliest starting subtask begins and when its latest
finishing subtask ends. It is not the simple arithmetic sum of the subtask
durations. Given the near infinite number of possible combinations of
links, overlaps, timings, and other factors that affect the start and end of
the individual subtasks, there could be dozens of possible reasons why the
summary doesn't begin and end exactly at the start or end of workday.