Leveling Question

M

Michael

I'm quite new to project. Is there a way to tell project to level
assignments without splitting specific tasks? The tasks can be delayed but I
don't want them split.

Thanks,

Michael
 
J

JulieD

Hi Michael

untick the "Levelling can create splits in remaining work" check box in the
levelling screen

Cheers
JulieD
 
B

Bob L

Under Tools|Level Resources.... , uncheck the box at the bottom of the
window that is labeled, 'leveling can create splits in remaining work'.

Regards,
Bob
 
M

Michael

But I want some tasks to be split and other specific ones not to be split.
That would prevent all from being split. Correct?

Thanks,

Michael
 
J

JulieS

Hi Michael,
In addition to JulieD's comments you may also add the field "Leveling Can
Split" to a task view and control on a task-by -task basis whether the task
may be split or not.

Hope this helps. Let us know how you get along.

JulieS
 
J

JulieD

Hi Julie

if you do this, should the check box in the level resource screen be checked
or unchecked?

Cheers
the other Julie
 
J

JulieS

Hi Julie,

If "Leveling Can Split" is set to "No" and the check box in the level
resources screen is enabled (checked) then only tasks with "Yes" in the
"Leveling Can Split " can be split. This would allow Michael to split some
tasks but not others.

Cheers,
Julie
The "Other" other Julie
 
S

Steve House [MVP]

In addition to the other comments. since you want some tasks to split and
others not to, do the leveling in several passes, selecting the tasks to be
leveled in the current pass and using "Level Selevcted Tasks" instead of
leveling the entire project.
 
G

Glen Howie

Ok, this leveling thing seems to be very elusive. What I want to do is Level
a set of 4 tasks, each one takes 4 hours, and they're all assigned to the
same person. So I want the tasks to be scheduled sequentialy, one after
another. If I set the resource to 80%, I would expect all 4 tasks to take
16/6 days to complete, but it seems to schedule them all on the same day. Is
there any way to default all tasks to only be done one at a time?

thanx . . . . . . . Glen
 
J

Jan De Messemaeker

Hi Glen,

Normally Leveling WILL sequence the tasks.
It is hard to say what causes your problem.
Are you sure you went through Tools, Resource Leveling, Level Now?
If yes, do not hesitate to send me the file, I'll take a look.
(You can "decypher" my e-mail address or find it on my website)
HTH
 
S

Steve House [MVP]

All levelling does is shift tasks so as to delay some of the work. It never
adjusts anything else, only delays the start time of one or more tasks.

For simplicity let's say Joe works 8 hours a day. I assign him at 100% to
two different tasks currently scheduled for Monday, each of which will take
8 hours to complete. The means he is being asked to somehow magically do 16
man-hours of work during one single 8-hour time period, obviously something
impossible. When I do resource levelling, Project will take ONE of those
tasks and push it over to Tuesday instead of Monday. It'll make up its own
mind about which one it chooses to move, but if it's important to me for one
of them to be done before the other, I can set the priority on the task I
want done first to something higher than the priority on the other task.

In your case, you have 4 tasks, Tasks 1, 2, 3, and 4, all 4 hours each, and
the same resource is assigned on each at 80%. Perhaps they all start off
scheduled beginning Monday at 8am and show finishing at 12 noon. You didn't
say what the resource's Maximum Availability setting is but if it's between
80% and 100% it doesn't matter and for an individual it should never be more
than 100%. The instantaneous committment level at any point in time can
never exceeed the maximum availability. So as it stands before leveling,
Joe is working 8am to 12 noon on Monday but he's expected to be doing 4
things all at once, representing a required committment of 320% but he's
only capable of doing much less. When you level, the tasks will stagger out
so #1 remains on Mon 8am - 12noon, #2 is Mon 1pm-5pm, #3 is Tue 8am-12noon,
and #4 is Tue 1pm-5pm. On the other hand, if Joe's maximum availability is
LESS than 80%, Project balks and gives you an error message. Why? Even if
you just look at one of those tasks, you have scheduled Joe to work 80% when
his maximum is only 50%. There is no way leveling can SHIFT that task to
bring Joe's instantaneous commitment down to 50% - even staggering the
multiples leaves him at 80% during each task. The only thing that will
reduce it farther that is to EXTEND the tasks and make each of them take
longer (because a lower percentage means he's working slower on the task) as
well as move some of them. But that's simply not what levelling does, ever.
It has no way of knowing if that would even be an option because it doesn't
know what else might be going on that's not part of the project so it gives
you an "I can't fix it" message and kicks it back into your court for you to
handle by hand.

Don't make the mistake of thinking an assignment of "80%" means he works on
the project tasks 6 hours a day out of each 8 hour work day. Likewise a
maximum of 80% doesn't mean he's only availble to work on the project 6
hours out of each day. It does mean the equivalent of that, in a way, but
it's actually a little more subtle the way it works. An assignment of 80%
means that he is not working at full speed for some reason (not necessarily
slacking off, maybe he has other demands on his plate at the same time).
That means that during any arbitrary period of time, he can only convert 80%
of the time into man-hours of work. If we're looking at 1 week from the
task's start to finish, he'll produce 4 man-days of work, the amount of
output he COULD have done in 4 days if he had nothing else on his plate. If
he's assigned 80% to a 4-hour duration task, it mean he's going to be able
to generate a little over 3 man-hours worth of equivalent full-time output
over the course of working 4 hours. It does not mean he work's 3 hours - it
means he works 4 but only generates the output of 3 hours, 12 minutes
full-time work. If we say his maximum is 80%, that means we want to reserve
20% of his energy for other, unspecified stuff and we're gonna let him sort
it out for himself how he wants to prioritize his workday, meaning when we
assign him to an 8 hour long task, we're really only expecting him to
produce 6 man-hours of work, understanding that he is working on it
sandwiched in and amongst the other things he has to do.

HTH
--
Steve House [MVP]
MS Project Trainer & Consultant
Visit http://www.mvps.org/project/faqs.htm for the FAQs
 
G

Glen Howie

Wow, thanx Steve and Jan, I think in your lengthy responses that Project
should do what I want it to do. I should also point out that I did download
and install the "Project 2003 post-Service Pack 1 hotfix package: January 13,
2005" because the summary task rollups for work units was not working
properly.
http://support.microsoft.com/default.aspx?scid=kb;en-us;891203#4

I think I will take Jan up on his offer and send him my mpp.

thanx again . . . . . . . Glen
 
G

Glen Howie

Just wanted to note that I did finally get this levelling to work, although
it only did so when I paid attention to the error messages and changed the
resource units to 50% on individual tasks. (Since my availability really
wasn’t going to be 80% anyway. )

Steve and Jan make the excellent point that using Project doesnt necessarily
make you a project manager and some basic training on the tool at least is
highly recommended. (also read Jan's Top 10 list on his web site).

thanx . . . . . . . Glen
Microsoft CRM Product Specialist
 
S

Steve House [MVP]

I'm curious, why are setting your resource's maximum's and assigning them at
less than 100% anyway? Sometimes there are good reasons to do that but it
seems like you might be trying to micromanage here. A resource assignment
of 50% means that when he's working on a task for 4 hours, he's going to get
done what he could have done in 2 hours if he'd devoted his full attention
to the job at hand. Why not make the task 2 hours long, assign him 100%,
expect him to work efficiently, and keep it all simple? When you say "I
wonder how long it'll take Joe to do this?" when you're estimating
durations, you kind of subconsciously build an allowance for Joe's quirks
and foibles into your estimate anyway, so your idea of Joe for X hours @
100% kind of already takes into account that he's going to have to answer
emails, take a phone call or two, or take a bathroom break while he's
working on the task. I'm a big believer in having those estimates based on
some reality and not just plucked out of thin air. The best reality to look
at is previous tasks of a similar nature. If you look back to last year's
Big Rollout and see that installing 10 widgets took 3 days and in this
year's upgrade you have 25 widgets to install, it'll probably take you about
9 days to do it. That estimate already has a built in allowance for the
inevitable distractions a widget installer will face since it's a pretty
good bet that the work this year is going to progress similar to the way it
went last year. You may not know whether your installer is working at 100%
or not but looking at it this way it doesn't really much matter. You just
assume that what he typically does on tasks of this nature represents 100%.
Or if you don't have a historical record but this year you go to Joe
Installer amd ask him "How long do you think it'll take you to install 25
widgets?" and he scratches his head and says "Should be 9 or 10 days," again
he's kind of built-in those allowances for distractions. Don't think it
terms of how much time is budgeted, think in terms of how much time will be
required.

--
Steve House [MVP]
MS Project Trainer & Consultant
Visit http://www.mvps.org/project/faqs.htm for the FAQs
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top