Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Microsoft Project Resource Level Quandry

Status
Not open for further replies.

gregsedwards

Instructor
Jan 10, 2002
11
US
In a Project file, suppose I have three tasks, a, b and c. These tasks are fixed units and effort driven. "Me" is working 25% on each of these tasks. I have "Me" set as only 50% maximum availability.

At first, "Me" is overallocated (75% versus 50%). When I level the resources, task c is pushed out past a and b. This makes sense. The combination of a and b gives us 50%, which is the maximum "Me" is allowed. Now, suppose I change "Me" to have a 40% maximum allocation. When I level the resources, the three tasks are spread out so that none of them are being worked at the same time. I see the logic. Project thinks that "Me" can't work on both tasks at the same time because that would cause a 50% workload, which is now considered overallocated.

However, I would like for Project to take the extra 15% (40%-25%) and go ahead and use that to work on task B. The way it works now, the project plan says the end date is much later than it actually would be.

The only thing I know to do is to manually change "Me" to 15% on task B and relevel. This works, but when you have a project plan that has several hundred tasks with the same resources working on several at the same time, the math gets complicated if not impossible. Do you know of a way around this?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top