J
Jack Dahlgren MVP
Hit the F9 key and see what happens.
-Jack Dahlgren
-Jack Dahlgren
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
S
SProvost
I want to level my project but nothing happens.
A theory says it is because of contraints. I slected all tasks and set them
to as soon as possible.
It still does not work.
How can I level, so I can see when the project really ends?
A theory says it is because of contraints. I slected all tasks and set them
to as soon as possible.
It still does not work.
How can I level, so I can see when the project really ends?
J
Jan De Messemaeker
Hi,
There are so many ways to make leveling not work that this is guesswork.
Did you asisgn resources to all tasks?
Don't tasks have actual start dates?
Isn't calculation set to manual (that is the F9 trick to test)?
Aren't resources assigned to units higher than their max units?
Is priority of the tasks set to 1000?
Don't you have the leveling option "Level only within available slack" on?
Maybe I forget some..
--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
+32 495 300 620
For availability check:
http://users.online.be/prom-ade/Calendar.pdf
There are so many ways to make leveling not work that this is guesswork.
Did you asisgn resources to all tasks?
Don't tasks have actual start dates?
Isn't calculation set to manual (that is the F9 trick to test)?
Aren't resources assigned to units higher than their max units?
Is priority of the tasks set to 1000?
Don't you have the leveling option "Level only within available slack" on?
Maybe I forget some..
--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
+32 495 300 620
For availability check:
http://users.online.be/prom-ade/Calendar.pdf
S
SProvost
Wow, there are so many things to check. Do you mean that leveling will work
ONLY if I assign resources to all tasks AND I make sure all tasks have actual
start dates AND I set calculation to automatic AND resources are not assigned
to units higher than their maximum units AND task priority is NOT 1000 AND
the leveling option "Level only within available slack" is NOT on?
Did I get every one of these right? Or did I understand just the opposite of
what you meant, for some of these?
ONLY if I assign resources to all tasks AND I make sure all tasks have actual
start dates AND I set calculation to automatic AND resources are not assigned
to units higher than their maximum units AND task priority is NOT 1000 AND
the leveling option "Level only within available slack" is NOT on?
Did I get every one of these right? Or did I understand just the opposite of
what you meant, for some of these?
J
Jack Dahlgren MVP
If you set actual start dates then the project won't move those tasks
forward.
If you don't have resources on a task, then there is nothing to level those
tasks on.
Most of the the settings have some effect on leveling. The effects are
predictable and expected if you are familiar with leveling. If not, then you
won't see what you are expecting.
-Jack
forward.
If you don't have resources on a task, then there is nothing to level those
tasks on.
Most of the the settings have some effect on leveling. The effects are
predictable and expected if you are familiar with leveling. If not, then you
won't see what you are expecting.
-Jack
S
Steve House
Adding a note to Jack's comments, in addition to the points he made,
leveling resolves overallocations that are the result of a resource being
assigned to 2 or more concurrent tasks resulting in a total allocation that
exceeds his maximum. If he's assigned to a SINGLE task at more than his
maximum allocation leveling cannot fix it. This commonly occurs when Joe
has been assigned to tasks at 100% and then you find out he's only available
a max of, say, 50%. Updating his Maximum Allocation field on the Resource
Sheet to the new maximum does not ripple over to automatically change his
assignment level on tasks he's already been assigned to, instead merely
showing him as overallocated on them. He's assigned to Wax Widgets at 100%
but is only available a max of 50% - that sort of over must be resolved
manually on a task-by-task basis, leveling won't touch it.
leveling resolves overallocations that are the result of a resource being
assigned to 2 or more concurrent tasks resulting in a total allocation that
exceeds his maximum. If he's assigned to a SINGLE task at more than his
maximum allocation leveling cannot fix it. This commonly occurs when Joe
has been assigned to tasks at 100% and then you find out he's only available
a max of, say, 50%. Updating his Maximum Allocation field on the Resource
Sheet to the new maximum does not ripple over to automatically change his
assignment level on tasks he's already been assigned to, instead merely
showing him as overallocated on them. He's assigned to Wax Widgets at 100%
but is only available a max of 50% - that sort of over must be resolved
manually on a task-by-task basis, leveling won't touch it.
J
Jack Dahlgren MVP
Priority set to 1000 prevents tasks from being moved by leveling.
I can't figure out what your question is at the end.
-Jack Dahlgren
I can't figure out what your question is at the end.
-Jack Dahlgren
SProvost said:Thank you to all for your answers. It is reassuring that leveling will
resolve overallocations that are the results of the resource being
assigned
to concurrent tasks. This is what I am trying to solve.
Obviously the project has a start date. I marked all tasks to start as
soon
as possible. I assigned resources to all tasks. Calculation is set to
automatic. Priority of tasks is set to 500. That seems to be the default.
Does it need to be set to 1000?
The only leveling options on are: Leveling can adjust individual assign...
and the split work option.
Again, I really appreciate your help .
I am not sure what this means: Aren't resources assigned to units higher
than their max units?
Steve House said:Adding a note to Jack's comments, in addition to the points he made,
leveling resolves overallocations that are the result of a resource being
assigned to 2 or more concurrent tasks resulting in a total allocation
that
exceeds his maximum. If he's assigned to a SINGLE task at more than his
maximum allocation leveling cannot fix it. This commonly occurs when Joe
has been assigned to tasks at 100% and then you find out he's only
available
a max of, say, 50%. Updating his Maximum Allocation field on the
Resource
Sheet to the new maximum does not ripple over to automatically change his
assignment level on tasks he's already been assigned to, instead merely
showing him as overallocated on them. He's assigned to Wax Widgets at
100%
but is only available a max of 50% - that sort of over must be resolved
manually on a task-by-task basis, leveling won't touch it.
--
Steve House [Project MVP]
MS Project Trainer & Consultant
Visit http://project.mvps.org/faqs.htm for the FAQs
SProvost said:Wow, there are so many things to check. Do you mean that leveling will
work
ONLY if I assign resources to all tasks AND I make sure all tasks have
actual
start dates AND I set calculation to automatic AND resources are not
assigned
to units higher than their maximum units AND task priority is NOT 1000
AND
the leveling option "Level only within available slack" is NOT on?
Did I get every one of these right? Or did I understand just the
opposite
of
what you meant, for some of these?
:
Hi,
There are so many ways to make leveling not work that this is
guesswork.
Did you asisgn resources to all tasks?
Don't tasks have actual start dates?
Isn't calculation set to manual (that is the F9 trick to test)?
Aren't resources assigned to units higher than their max units?
Is priority of the tasks set to 1000?
Don't you have the leveling option "Level only within available slack"
on?
Maybe I forget some..
--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
+32 495 300 620
For availability check:
http://users.online.be/prom-ade/Calendar.pdf
I want to level my project but nothing happens.
A theory says it is because of contraints. I slected all tasks and
set
them
to as soon as possible.
It still does not work.
How can I level, so I can see when the project really ends?
S
SProvost
Thank you to all for your answers. It is reassuring that leveling will
resolve overallocations that are the results of the resource being assigned
to concurrent tasks. This is what I am trying to solve.
Obviously the project has a start date. I marked all tasks to start as soon
as possible. I assigned resources to all tasks. Calculation is set to
automatic. Priority of tasks is set to 500. That seems to be the default.
Does it need to be set to 1000?
The only leveling options on are: Leveling can adjust individual assign...
and the split work option.
Again, I really appreciate your help .
I am not sure what this means: Aren't resources assigned to units higher
than their max units?
resolve overallocations that are the results of the resource being assigned
to concurrent tasks. This is what I am trying to solve.
Obviously the project has a start date. I marked all tasks to start as soon
as possible. I assigned resources to all tasks. Calculation is set to
automatic. Priority of tasks is set to 500. That seems to be the default.
Does it need to be set to 1000?
The only leveling options on are: Leveling can adjust individual assign...
and the split work option.
Again, I really appreciate your help .
I am not sure what this means: Aren't resources assigned to units higher
than their max units?
Steve House said:Adding a note to Jack's comments, in addition to the points he made,
leveling resolves overallocations that are the result of a resource being
assigned to 2 or more concurrent tasks resulting in a total allocation that
exceeds his maximum. If he's assigned to a SINGLE task at more than his
maximum allocation leveling cannot fix it. This commonly occurs when Joe
has been assigned to tasks at 100% and then you find out he's only available
a max of, say, 50%. Updating his Maximum Allocation field on the Resource
Sheet to the new maximum does not ripple over to automatically change his
assignment level on tasks he's already been assigned to, instead merely
showing him as overallocated on them. He's assigned to Wax Widgets at 100%
but is only available a max of 50% - that sort of over must be resolved
manually on a task-by-task basis, leveling won't touch it.
--
Steve House [Project MVP]
MS Project Trainer & Consultant
Visit http://project.mvps.org/faqs.htm for the FAQs
SProvost said:Wow, there are so many things to check. Do you mean that leveling will
work
ONLY if I assign resources to all tasks AND I make sure all tasks have
actual
start dates AND I set calculation to automatic AND resources are not
assigned
to units higher than their maximum units AND task priority is NOT 1000 AND
the leveling option "Level only within available slack" is NOT on?
Did I get every one of these right? Or did I understand just the opposite
of
what you meant, for some of these?
S
Steve House
Resources should never be assigned at units in excess of their max units.
It's unfortunate that Project lets you get away with it if you try but
that's the way it is. The assignment percentage represents the rate at
which the resource converts working time into useful work output. A task
with a duration of 8 hours that has a resource assigned at 125% means that
somehow over the course of the 8 hours of time that the task is taking start
to finish, the resource magically produces 10 man-hours of useful work,
doing the work of 1 and 1/4 men, an obvious impossibility for anyone other
than a superhero <g>.
--
Steve House [Project MVP]
MS Project Trainer & Consultant
Visit http://project.mvps.org/faqs.htm for the FAQs
It's unfortunate that Project lets you get away with it if you try but
that's the way it is. The assignment percentage represents the rate at
which the resource converts working time into useful work output. A task
with a duration of 8 hours that has a resource assigned at 125% means that
somehow over the course of the 8 hours of time that the task is taking start
to finish, the resource magically produces 10 man-hours of useful work,
doing the work of 1 and 1/4 men, an obvious impossibility for anyone other
than a superhero <g>.
--
Steve House [Project MVP]
MS Project Trainer & Consultant
Visit http://project.mvps.org/faqs.htm for the FAQs
SProvost said:Thank you to all for your answers. It is reassuring that leveling will
resolve overallocations that are the results of the resource being
assigned
to concurrent tasks. This is what I am trying to solve.
Obviously the project has a start date. I marked all tasks to start as
soon
as possible. I assigned resources to all tasks. Calculation is set to
automatic. Priority of tasks is set to 500. That seems to be the default.
Does it need to be set to 1000?
The only leveling options on are: Leveling can adjust individual assign...
and the split work option.
Again, I really appreciate your help .
I am not sure what this means: Aren't resources assigned to units higher
than their max units?
Steve House said:Adding a note to Jack's comments, in addition to the points he made,
leveling resolves overallocations that are the result of a resource being
assigned to 2 or more concurrent tasks resulting in a total allocation
that
exceeds his maximum. If he's assigned to a SINGLE task at more than his
maximum allocation leveling cannot fix it. This commonly occurs when Joe
has been assigned to tasks at 100% and then you find out he's only
available
a max of, say, 50%. Updating his Maximum Allocation field on the
Resource
Sheet to the new maximum does not ripple over to automatically change his
assignment level on tasks he's already been assigned to, instead merely
showing him as overallocated on them. He's assigned to Wax Widgets at
100%
but is only available a max of 50% - that sort of over must be resolved
manually on a task-by-task basis, leveling won't touch it.
--
Steve House [Project MVP]
MS Project Trainer & Consultant
Visit http://project.mvps.org/faqs.htm for the FAQs
SProvost said:Wow, there are so many things to check. Do you mean that leveling will
work
ONLY if I assign resources to all tasks AND I make sure all tasks have
actual
start dates AND I set calculation to automatic AND resources are not
assigned
to units higher than their maximum units AND task priority is NOT 1000
AND
the leveling option "Level only within available slack" is NOT on?
Did I get every one of these right? Or did I understand just the
opposite
of
what you meant, for some of these?
:
Hi,
There are so many ways to make leveling not work that this is
guesswork.
Did you asisgn resources to all tasks?
Don't tasks have actual start dates?
Isn't calculation set to manual (that is the F9 trick to test)?
Aren't resources assigned to units higher than their max units?
Is priority of the tasks set to 1000?
Don't you have the leveling option "Level only within available slack"
on?
Maybe I forget some..
--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
+32 495 300 620
For availability check:
http://users.online.be/prom-ade/Calendar.pdf
I want to level my project but nothing happens.
A theory says it is because of contraints. I slected all tasks and
set
them
to as soon as possible.
It still does not work.
How can I level, so I can see when the project really ends?
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.