Complete a task before moving to next task.

[Mike Jones]

I'm confused.

I'd like to specify a number of tasks, give them each an amount of work,
then assign them to a resource. I'm expecting that leveling should
move the start and end dates of the tasks so that the resource
consistently has their assigned % of work. The tasks should follow one
another--one should be completed before the next one starts.

Instead, I'm seeing the tasks start in parallel. Project tweaks the
assign resources percentages to reflect that. So I go in and change the
% back to whats expected.

Rather than level the tasks, the resource is grossly overallocated, with
the tasks still in parallel.

What needs to happen here? I could put in dependencies, but I don't
think that's necessarily the best way to solve the problem. I want
Project to do the scheduling for me!

Thanks.

 

[Gerard Ducouret]

Hello Mike,
Did you tried the "Level Resources" feature :
Tools / Level Resources... / Level Now
what are the settings you selected in the Resource Leveling dialog box ?

Gérard Ducouret

 

[Jan De Messemaeker]

Hi Mike,

You just have invented a new Project!
AFAIK up to now, leveling does not change any allocation percentages, it
just postpones tasks with move priority than others.
I really fail to understand what you are describing, but I'm pretty sure
it's not Project's leveling I'm afraid.
HTH

 

[Mike Jones]

Very odd. I've been reading other posts that say this also, but its not
the case. The leveling did in fact change my allocations to weird
things like 13%, 26%, etc., etc.

As I say, can I make Project complete one task and move on to the next,
leaving the resource allocated correctly? Its not postponing the tasks
at all, its doing them all in parallel and just shifting resource
allocation. That is very close to useless to me.

 

[Mike Glen]

Yes, Mike, by levelling: Tools/Resource levelling/Level Now.


Mike Glen
Project MVP

 

[Mike Jones]

That's exactly what I'm doing. That is what gives me the bizarre
resource allocations. All I can figure is I have some unusual global
setting messed up.

The way this thing works seems really inconsistent. In previous groups
of tasks, in the same project, it has seemed to work fine. For this
group, the only thing that would work was to put in artificial dependencies.

 

[Mike Glen]

Hi Mike,

If you can zip up the file and email it to me, I'll have a look and see if I
can find out what's going on.

Mike Glen
Project MVP

 

[Gordon Blair]

Mike,

Have you prioritised the tasks? Just a hunch, but if all tasks have the
same priority (500 for example), no other constraints or dependencies, MSP
will probably try to complete them all at the same time, in a fair and
equitable manner (by spreading you resource thinner than a supermodel on a
diet). If you really, really don't want to introduce finish to start
relationships, a variance in priority SHOULD (he said!), should level the
tasks properly when you go through the whole procedure.

Let me know how you get on, am curious

Cheers,

Gordon

 

[Sarah]

Mike,

In your original posting, you state that the tasks should follow one
after the other. This sounds to me like there *should* be dependencies
in there. Why do you say they would be artificial dependencies?

Sarah

 

[Mike Jones]

Okay--found the problem...it is ME!

What's going on is that the resource I was assigning to the task was no
longer available after 11/30...so I guess project was doing its best to
cram the work into the remaining time. Anyway, after making the
resource available for a longer period of time (relecting new
realities!), the tasks fall after each other as expected...without
having explicit dependencies.

Thanks for the suggestions...and the firm assertions that it CAN work
right. There's just still more that I have to learn. I'm both
fascinated and frustrated at the complexity of the app!

 

[Mike Glen]

Hi Mike,

Glad you've got it sorted and thankks for the feedback. Good Luck

Mike Glen
Project MVP

 

[Jan De Messemaeker]

Hi Gordon,

No, no, no, no, sorry.
Leveling does not spread resources. Never.
It ONLY delays tasks when necessaruy.
HTH