Leveling delays wont adjust automatically and default assignmentunits..

[Gil]

Hi all,
I have 2 problems, and I will appreciate any help:

1)
As an example, assume I have only two assignment: A (50 hours) and B
(20 hours), and both are assigned to the same resource, with no
dependencies or other constraints. Since my resource has the default 8
hours calendar and max units of 100%, he will be over-allocated,
because both tasks are scheduled to the project start date.
After leveling this resource task B is delayed and starts when task A
is finished, and the resource is not over-allocated anymore. So far so
good, but...
Assume that task A is only 8 hours. I change the work field to 8 hours
(all tasks are fixed work type), and duration is shortened to only 1
day, but task B is still far in the future, based on the leveling
delay that was created before, even though now only a leveling delay
of one day is required, and not of 8 days, meaning the tasks do not
start as soon as possible... the solution is to level resources again,
and now the tasks will again start as soon as possible. but if this is
the solution it means that after every change in the plan I need to
level resources again and again to make sure nothing is being delayed
for no reason?!
I guess Automatic leveling can solve this issue, but it is not
recommended at all...

2)
I created two generic resources in the resource sheet. QA (max units
of 30%) and DEV (max units of 200%). Why, when I assign them to tasks,
the default assignment units of QA is 30% (like max units) but the
default assignment units of DEV is 100% (not like max units, which is
300%)? Why do I have to manually change this to 300%? why isn`t the
default assignment units equals max units also when it is above 100%?

Thanks,
Gil

 

[JulieS]

Hello Gil,

In answer to your first question -- yes, if you have delayed work through
leveling, the easiest way is to relevel the resource to see Task B shift back
to earlier. You can certainly add the leveling delay field to a task view
and manually change the leveling delay if you prefer.

In answer to your second question, Project will pick the max. units when
assigning a resource if the max. units are 100% or less. Project will assign
the 100% if max. units are greater than 100%. You may find working with the
task form visible at the lower portion of the screen helps with the
assignments.

I hope this helps.

Julie

 

[Jan De Messemaeker]

Hi Gil,

As for your first question, first, generally you will enter more than one
update so you don't havethat often. The only other way to save time is to
create a macro calling for resource leveling and link it to a new button on
a toolbar, which will reduce leveling to a one click operation.

Secondly, I really wonder how you can hope for an explanantion on what
drives software developers in the lab? I can't imagine a WHY, but does it
matter? This is how it works, and we can't change it :-(

Hope this helps,

--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
+32 495 300 620
For availability check:
http://users.online.be/prom-ade/Calendar.pdf

 

[Gil]

Hi Gil,

As for your first question, first, generally you will enter more than one
update so you don't havethat often. The only other way to save time is to
create a macro calling for resource leveling and link it to a new button on
a toolbar, which will reduce leveling to a one click operation.

Secondly, I really wonder how you can hope for an explanantion on what
drives software developers in the lab? I can't imagine a WHY, but does it
matter? This is how it works, and we can't change it :-(

Hope this helps,

--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
+32 495 300 620








- Show quoted text -

Thank you both for helping me with your answers.
Jan, I was not hoping to understand the way developers think.. I was
just wondering weather I am doing something wrong, or maybe there is
another way of doing it right, or maybe an explanation why this
behaviour of the tool is actually good for me.
Thanks again,
Gil