Loading...
Quick Links

Reply To: MS Project Scheduling

Home Forums Discussion MS Project Scheduling Reply To: MS Project Scheduling

#414533

Debra;
Summary tasks types are set by MS Project and can’t be manipulated by the PM so don’t worry about them.

In your original question, you mentioned that durations are being calculated wrong. Let me point you to another article that discusses how Project actually determines a task duration.
http://www.mpug.com/articles/how-microsoft-project-calculates-task-duration/

In short, Duration in project actually means only days on which work is scheduled to occur. So in your example, you have 10 days of work spread over several months. There could be many reasons for this.
One is that the planned work is being split many times (1 hour this week, 1 hour next week, etc.) and the calendar duration is several months but the task duration shows 10 days because there are only 10 days in that task on which work is scheduled. This scenario is the article I referenced earlier.
However, if there IS work scheduled on each day across several months (.1 hr/day for example) this could be caused by many things such as;
* Dependency relationship: Task B is a successor of A. A starts Jan 1, and B Starts March 1. In this case Project can spread the work from A across several months without impacting critical path/completion date.
* Multiple resources assigned: 5 resources each have 40 hours on Task A, but because of other tasks, each resource is working on Task A at different times.
* Task priorities/leveling: Other tasks have a higher leveling priority field value or because of how Project levels, Task A is a lower priority in the leveling algorithm. As a result, Task A can be spread.
* Assignment Units: Lets say Bob has a max units of 100%. Bob is on critical path tasks with an assignment units of 95% and on Task A (the one being spread) at 100%. Because the other tasks are scheduling first, Project can only allocate 5% of Bobs time on any day to Task A.

Here’s some debugging questions that might help;
* Does it matter that your VBA Bus Contracts task takes 90 days to complete? If not, maybe you do nothing to fix it.
* Is this simply confusion about why 10 days of work is being scheduled across 90 days? Unfortunately, this starts getting into the details about how MS Project levels resources and the configuration/option settings you’ve selected.
* If it must be completed in 10 days, then maybe this is a candidate for a higher leveling priority value at the task level (and change your leveling to use Priority,Standard).
* What else is occurring at the same time in the schedule for the VA Bus Contracts assigned resources? Those tasks may be taking almost all the resources Max Units availability, but leaving a small amount of availability that the VBA Bus task is filling. Use the Resource Usage view set up on a daily timescale to see which other tasks are being allocated work for those VBA Bus resources at the same time. Maybe there’s an incorrect dependency causing those tasks to schedule earlier than needed. Sometimes just seeing where the work IS being allocated will point you to an answer.

Bottom line, without seeing the schedule, it’s hard to pinpoint the root cause of the issue.
I tried to map out some of the questions I’d ask if I were looking at the schedule with you.
Hopefully they may help you identify the cause.

Hope this helps