Dose the longest task start first by default?

[Michael Hsing]

Hello,
It seems by default the longest task (by the same resource) will start first.

For example,
1. Create task1 with duration of 2 days.
2. Create task2 with duration of 4 days.
3. Assign r1 to task1. It shows task1 starts on 10/27.
4. Assign r1 again to task2. Now task2 will start on 10/27, and task1 will
start on 11/2.

Is there an option I can specify that the task I add first ( like task1)
will start first, if I don't specify any dependency/predecessors between the
tasks?

Thanks for the help.

Regards,
Mike

 

[Gerard Ducouret]

Hello Michael,

Have you set the Leveling calculation to "Automatic" ?
If yes, go to Tools / Level resources... / Calculation : manual

Then create a Finish to Start link (FS) in the Predecessor column.
If you want to use the leveling tool, you can also use the Priority setting
in the Task information dialog box, General tab. the default Priority is 500
for all the tasks. The highest priority is 1000.

Hope this helps,

Gérard Ducouret [Project MVP]

 

[Michael Hsing]

Hi Gerard,
Thank you very much. Yes, I was using the automatic Leveling. I believe this
is the default. Is it common to turn it off?
Mike.

Hello Michael,

Have you set the Leveling calculation to "Automatic" ?
If yes, go to Tools / Level resources... / Calculation : manual

Then create a Finish to Start link (FS) in the Predecessor column.
If you want to use the leveling tool, you can also use the Priority setting
in the Task information dialog box, General tab. the default Priority is 500
for all the tasks. The highest priority is 1000.

Hope this helps,

Gérard Ducouret [Project MVP]

Hello,
It seems by default the longest task (by the same resource) will start first.

For example,
1. Create task1 with duration of 2 days.
2. Create task2 with duration of 4 days.
3. Assign r1 to task1. It shows task1 starts on 10/27.
4. Assign r1 again to task2. Now task2 will start on 10/27, and task1 will
start on 11/2.

Is there an option I can specify that the task I add first ( like task1)
will start first, if I don't specify any dependency/predecessors between the
tasks?

Thanks for the help.

Regards,
Mike

 

[Steve House [MVP MS Project]]

My 2 cents - it is STRONGLY advised to turn off automatic leveling. If you
don't and you assign a resource to a task in such a way that it creates an
overallocation, Project will immediately move one of the offending tasks to
resolve the problem. The result is tasks flying about the screen without
apparent rhyme or reason. MSP isn't a mind reader and for all it knows, you
might have been just about to do something else, add a task or link or
change another resource that would have fixed the problem anyway. Far
better to have leveling set to manual and trigger it yourself when you're
ready for it to do its thing.

Steve House [MVP]

Hi Gerard,
Thank you very much. Yes, I was using the automatic Leveling. I believe
this
is the default. Is it common to turn it off?
Mike.

Hello Michael,

Have you set the Leveling calculation to "Automatic" ?
If yes, go to Tools / Level resources... / Calculation : manual

Then create a Finish to Start link (FS) in the Predecessor column.
If you want to use the leveling tool, you can also use the Priority
setting
in the Task information dialog box, General tab. the default Priority is
500
for all the tasks. The highest priority is 1000.

Hope this helps,

Gérard Ducouret [Project MVP]

Hello,
It seems by default the longest task (by the same resource) will start first.

For example,
1. Create task1 with duration of 2 days.
2. Create task2 with duration of 4 days.
3. Assign r1 to task1. It shows task1 starts on 10/27.
4. Assign r1 again to task2. Now task2 will start on 10/27, and task1 will
start on 11/2.

Is there an option I can specify that the task I add first ( like
task1)
will start first, if I don't specify any dependency/predecessors
between the
tasks?

Thanks for the help.

Regards,
Mike

 

[Michael Hsing]

Hi Steve,
Thank you so much. This advice is very helpful.
Mike.

My 2 cents - it is STRONGLY advised to turn off automatic leveling. If you
don't and you assign a resource to a task in such a way that it creates an
overallocation, Project will immediately move one of the offending tasks to
resolve the problem. The result is tasks flying about the screen without
apparent rhyme or reason. MSP isn't a mind reader and for all it knows, you
might have been just about to do something else, add a task or link or
change another resource that would have fixed the problem anyway. Far
better to have leveling set to manual and trigger it yourself when you're
ready for it to do its thing.

Steve House [MVP]

Hi Gerard,
Thank you very much. Yes, I was using the automatic Leveling. I believe
this
is the default. Is it common to turn it off?
Mike.

Hello Michael,

Have you set the Leveling calculation to "Automatic" ?
If yes, go to Tools / Level resources... / Calculation : manual

Then create a Finish to Start link (FS) in the Predecessor column.
If you want to use the leveling tool, you can also use the Priority
setting
in the Task information dialog box, General tab. the default Priority is
500
for all the tasks. The highest priority is 1000.

Hope this helps,

Gérard Ducouret [Project MVP]


"Michael Hsing" <[email protected]> a écrit dans le
message de Hello,
It seems by default the longest task (by the same resource) will start
first.

For example,
1. Create task1 with duration of 2 days.
2. Create task2 with duration of 4 days.
3. Assign r1 to task1. It shows task1 starts on 10/27.
4. Assign r1 again to task2. Now task2 will start on 10/27, and task1
will
start on 11/2.

Is there an option I can specify that the task I add first ( like
task1)
will start first, if I don't specify any dependency/predecessors
between
the
tasks?

Thanks for the help.

Regards,
Mike