Wrong Finish Dates?

[Patrick Peters]

I'm running project 2000. I've got a resource that I have set up as 40%
available (using Max Units on the resource sheet). I assign this resource
to a 40 hr task. Project computes the finish date as if the resource was
100% available to the project. What am I doing wrong? I've tried
levelling, but that doesn't seem to help.

Thanks

Pat

 

[Gérard Ducouret]

Hello Patrick,

Where did you enter these 40 hrs : in the Duration field or in the Work
field ?
If you entered thes 40hrs in the duration, so this task didn't have any
work, the software assign by default the resource with units = 1 (1 person
full time) or less than 1 if the Maxi Unit is less than 1.

Gérard Ducouret

 

[Patrick Peters]

That was exactly my problem. I'm moving the information I entered from the
Duration column to the Work column. This is the first project I've worked
on where I had to do that.

Thanks for the help.

Pat

 

[Jan De Messemaeker]

Dag Patrick,

One more remark; it is really important that you set the expectation for
leveling right.
Leveling ONLY DELAYS ASSIGNMENTS to solve overallocations, it never ever
changes assignment units.

Hope this helps,

--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
Project Management Consultancy
Prom+ade BVBA
32-495-300 620

 

[Patrick Peters]

Thanks for the reminder.

Pat

Dag Patrick,

One more remark; it is really important that you set the expectation for
leveling right.
Leveling ONLY DELAYS ASSIGNMENTS to solve overallocations, it never ever
changes assignment units.

Hope this helps,

--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
Project Management Consultancy
Prom+ade BVBA
32-495-300 620

 

[Steve House]

When you enter a task you also enter a duration estimate. Remember work and
duration are fundamentally different measures and are not interchangeable.
When you subsequently assign a resource, Project assumes you had whatever
assignemnt percentage you designate in the initial assignmant as what you
had in mind all along when you made the original duration estimate. For
example, If I enter the task with a 5 day duration and then assign a
resource at 50%, Project assumes I was planning on putting someone on it at
50% when I typed in that 5 days. If not, I would have estimated it at
something else. As a rule, Project *never* changes the task's duration on
the *initial* resource assignment. Subsequent *edits* to the resource
assignments will trigger recalculation, to exactly what end result depending
on the nature of the change and on task type and effort driven settings.