But what is wrong with splitting the task into smaller tasks, one task for
each resource assigned to it? That way it become a no brainer to update the
baseline for the one resource's work if this is one of those odd cases where
it is required?
The way I explain it to my classes, consider where a computer classroom
needs to be painted. If the painter and his assitant are going to be the
ones to disconnect and move the computers, move out the furniture, take
fixtures off the wall, blend the colour, and apply the paint, then move
everything back in again, you can show it as one task "paint the room" and
assign the painter and assistant to it. But if some techs from IT are going
to disconnect the computers, labourers from maintainance come in to move the
furniture, a carpenter to take down the wall fixtures, a colour specialist
to blend the paint, plus the painter and his assistant to apply the paint,
you need to break it down into all its separate component activities so each
one can be scheduled as a distinct task. From the way you present your
problem it sounds like you have a task listed as a single task like in the
first case but resources who actually do different things assigned to it
like the second. I strongly suspect that is the root of your problem. If
there are 5 resources assigned to that task, you need to split it into 5
different tasks, one for each resource, perhaps grouped together as subtasks
under one summary task. If you do that, it's extremely simple to rebaseline
the one task/resource out of the group that has changed.
Your project task list isn't complete until it details every individual
specific physical activity performed by a single "skill package."
--
Steve House [MVP]
MS Project Trainer & Consultant
Visit
http://www.mvps.org/project/faqs.htm for the FAQs
