Why does auto schedule insist on making the longest task happen first?



I make a simple list of tasks, which must take place in a particular order.

They have varied lengths, yet when I auto schedule, the Gant view shows me that the longest starts first, then the second longest, and so on.

The only way I can avoid this happening is by manually linking tasks but I fear doing it this way the project file will quickly become unmanageable.

What is the correct thing to do in ths situation?

Hello Project64,

I'm a bit baffled by your comment -
If the tasks must take place in a particular order, the only way of accomplishing that is to create predecessors and successors.

I'm also not following your comment about "autoschedule" tasks are either manually scheduled or autoscheduled. Are you referring to resource leveling?

If there is a required sequence, tasks should be linked. If there is no required sequence and you want to influence the order of tasks and the tasks create overallocations, modify the priority of the tasks and then use the resource leveling command with "priority, standard" order.

Post back with some more details about what you are trying to accomplish and we'll try to assist.

Julie

I know what you are asking about, I have a similar situation. The tasks are not necessarily dependent, but it is much easier to look at the project (especially for PHBs) if the tasks are scheduled in the order they appear on the plan. Otherwise way down at the task list is the first task if it is a large task.

What you want to do is on the Resource Tab => Leveling Options => Leveling Order. Set this to ID Only. Then, re-level the project. This will prioritize the ID as the order of scheduling, constraints not withstanding.

Assuming the OP has resources assigned, that should work well.