Levelling Tips Case
Essay by Woxman • September 26, 2012 • Study Guide • 483 Words (2 Pages) • 1,683 Views
LEVELING RESOURCES IN PROJECT
To solve over allocation of a resource (shows up as red on the resource sheet for both 2007 and 2010 versions), one can delay a task using the number of slack days it has (leveling within slack) or split a resource's work on a task which is called leveling outside of slack. You have a choice in Project to do either one.
Doing either leveling within or leveling outside slack does not change who is assigned nor should change task duration. You need to check the duration times of your tasks after leveling to make sure those durations have not inadvertently been changed. If so change them back.
Make sure you save two different files (one for Leveling within slack and one for leveling outside slack) from previous Zuma file.
FOR LEVELING RESOURCES WITHIN SLACK
* 2010 version
o Resource tab > in level group >Click on leveling options
o Manual selected
o Level entire project
o Check level only within available slack
o Unclick everything else
o Check Clear leveling values before leveling
o Click OK
o If box pops up with "cannot resolve the over allocation...." , then click Skip All
* 2007 version
o Tools tab > Resource Leveling
o Manual selected
o Level entire project
o Check level only within available slack
o Unclick everything else
o Check Clear leveling values before leveling
o Click OK
o If box pops up with "cannot resolve the over allocation...." , then click Skip All
FOR LEVELING RESOURCES OUTSIDE OF SLACK
* 2010 version
o Resource tab > in level group > click on leveling options
o Manual selected
o Level entire project
o Check level can adjust individual assignments ( you cannot create splits)
o Unclick everything else
o Check Clear leveling values before leveling
o Click OK
o If box pops up with "cannot resolve the over allocation...."
...
...