Solved

MS Project 2013 auto schedule duration

Posted on 2014-12-22
287 Views
I am a bit confused on how MS Project calculates the duration for the auto schedule for a summary task. Attached is the snapshot of my tasks. For the summary task, it summarizes as 20.38 days from 1/19 to 2/16. But the duration for all the tasks adds up to 16 hrs. I was expecting 2 days or 16 hrs for the duration for the summary task.
Capture.JPG
0
Question by:leblanc
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

• Help others & share knowledge
• Earn cash & points
• 2

LVL 48

Accepted Solution

PortletPaul earned 500 total points
ID: 40513811
DURATION is the measurement, in calendar units, between a start point and a completion point, but MSP (and most PM software) ignore non-work days when calculating duration.

So, if something starts January 19, and completes on February 16

Then "elapsed duration" is the days
19, 20, 21, 22, 23, 24, 25, 26, 27, 28 29, 30 , 31
+
1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16
+
3 hours

for "duration" remove Saturdays/Sundays and then
19, 20, 21, 22, 23,   26, 27, 28 29, 30
+
2, 3, 4, 5, 6,   9, 10, 11, 12, 13
+
3 hours
= 20.38 Days

For example, let's say we had  3 tasks, each takes 1 hour. They ALL can be conducted in parallel.

A summary of those tasks is  1 hour
|---------| summary

IF those tasks cannot be done in parallel then the summary duration is much larger:
``````|-----------------------------| summary
``````
You CANNOT simply add durations to arrive at the duration of a summary task, you MUST consider the span between start and end.
0

LVL 48

Assisted Solution

PortletPaul earned 500 total points
ID: 40513873
0

Featured Post

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

In our personal lives, we have well-designed consumer apps to delight us and make even the most complex transactions simple. Many enterprise applications, however, are a bit behind the times. For an enterprise app to be successful in today's tech wo…
"Disruption" is the most feared word for C-level executives these days. They agonize over their industry being disturbed by another player - most likely by startups.