Re: Leveling issues
- From: "Steve House [Project MVP]" <sjhouse.remove.this@xxxxxxxxxxxxxxxxxxx>
- Date: Fri, 17 Jun 2005 07:54:47 -0400
FYI - the "work" row in the usage views is the scheduled work. When you enter actual work in the usage voew, DO NOT just type it into the work row - be sure to add the Actual Work row to the view and enter the actuals there. Entering a value of XX hours in the actual row will update the work row to read the same but entering XX directly into the work row DOES NOT have the same consequences to the plan.
Q2 -- "Task C takes 70 hours" Is that duration or work? If it's duration and the resources are assigned 100%, you're saying that a resource is able to work 70 man-hours in 6 days???? That means he's working 12 hours a day, every day. Are you sure??? That's work conditions that border on the horrific. Allocation is the work expended over a period of time compared to the time itself. The calendar says how many hours a resource works when. If the resource's calendar is the standard 8 hour per day and you've scheduled him to do 12 hours of work in a day without explicitly saying part of it is overtime off the calendar, you've said he is doing 12 man-hours of work in 8 hours of time for an allocation of 150%, a physical impossibility. This sort of overallocation is not one that leveling can fix since leveling never adjusts the assignment percentages for you.
--
Steve House [MVP]
MS Project Trainer & Consultant
Visit http://www.mvps.org/project/faqs.htm for the FAQs
"kimg" <kimg @discussions.microsoft.com> wrote in message news:A8E81328-9616-4919-AE77-B3BDA9BBCB61@xxxxxxxxxxxxxxxx
I have a project of 600 tasks with 20 + resources. When I level, these are
the options set: Manual, Clear Leveling, Date Range, Level by ID, Leveling
can Adjust individual assignments on tasks and leveling can split.
1) I have project A and project B. I need to enter actual work for a task
so I go to the Task Usage Screen. For project A, I enter 8 hours for two
days. Project fills in 0's in the work field for the next day. For project
B, I enter the same 8 hours in on the same days, but Project fills in 8's in
the work fields for the next day. After leveling both projects, project A
finishe on 8/2. Project B finishes up on 7/26. Why the diference in end
days when the same process was applied to each project?
2) I have a task , task C that is 70 hours that has 3 resources working
part time. It should take approx 6 days for each of the resources to finish
up this task. There are two other tasks, task A and task D that the same
resources are assigned to. I level the project. Task A finishes up prior to
Task C. Task C splits 4 times and spans over 30+ days to finish. Task D is
incorporated into one of the splits of Task C, but why would this be when I
am leveling by ID? Shouldn't C finish before D? No dependencies. And, why
so many splits in the C task plus the huge gap in finishing this task?
3) I enter in actual work to the project plan. I level. I make two other
changes, minor changes to actual work, I level. I make no changes. I level.
Project recaculates my end date and all Milestones each time I level by a
few days. When there has not been that much actual work entered, why is
Project reshuffling dates and extending them each time I level. If there are
no changes in tasks 1 - 300, why does Project keep changing the dates of
those tasks everytime I level?
Thanks for the help.
.
- Follow-Ups:
- Re: Leveling issues
- From: nan
- Re: Leveling issues
- Prev by Date: Re: How do I accrue fixed material costs at the start of a task?
- Next by Date: Re: Microsoft Project Help
- Previous by thread: Re: Leveling issues
- Next by thread: Re: Leveling issues
- Index(es):
Relevant Pages
|
Loading
