My colleague approached me with an interesting question the other day. Under specific conditions, he could make seemingly identical tasks appear with different durations.
So the question is “why?” Why do seemingly identical tasks have different durations. First off, lets look at how duration is calculated…
Fixed Duration Activities Without Assignments
In the example below, I have three tasks. Each task is a different type.
You’ll note that the duration is the same. Next, I will introduce an exception of one day in the Project Calendar. In theory, this will push out the finish date for each task.
The results appear as below:
We see that the duration has not changed, even though the tasks now finish up on 6/13 instead of 6/10. This is as expected, because the duration is calculated as the total number of working days, and excludes any nonworking days such as weekends or holidays.
Fixed Duration Activities With Assignments
Now let’s assign a resource to each of those tasks.
Everything looks correct. The resource is using the same Project Calendar, and therefore, we anticipate no changes. Here’s where things get a bit trickier. I am going to add a 1 day exception to my resource calendar.
…and now my schedule looks like this:
See how the duration shows differently, yet for all intents and purposes, the start and finish dates are identical?
The reason for that is that Fixed Duration activities ignore the resource calendar when calculating duration. A Fixed Duration task calculates the difference between the start and end date using the Task or Project calendar. In this case, since I haven’t applied a Task calendar, the calculation uses the Project calendar.
Fixed Unit and Fixed Work tasks on the other hand, calculate duration by counting how many days on work is actually assigned.