Changes to baseline

S

Shaun

In my Project, my tasks have different resources from different departments.
Some of these resources want to change their baseline hours because of an
increase in scope. How do I change the baseline hours for 1 resource in a
task but leave the original baseline for the other resources? When I click
save baseline for the selected task, the baselines for all of the resources
change to the amount of work for the resources. Some of the resources have
been able to complete their portion of the task in less time than was
originally baslined and I want to be able to show this varience. Also how do
I get the Summary tasks of not only the sub set but the top levels to show
the increase?
 
P

Project Slave

Go to task usage view (views > more views > task usage)
Insert column (insert > column) baseline work
here, you can change baseline for some of the resources.
you can also see the changes to the summary task.

you can also insert another column for actual work for comparison purposes.
 
S

Steve House [MVP]

In essence the scope of a task is the deliverable the task produces. If you
have multiple resources assigned and it's even possible that the scope can
change for just one of them but not the others, that suggests they are all
producing different deliverables. That in turn suggests that you have
combined what really should be listed as completely separate and distinct
activities into one task and your WBS has not been sufficiently decomposed
into its activities. If you breakout the resource's task from the others,
listing them all as distinct activities, rebaselining that one task when its
scope changes becomes very simple.
 
S

Steve House [Project MVP]

IMHO, it is not possible for a scope change to trigger a change in hours for
1 resource out of a group assigned to a single task. "Scope" is the thing
that the task must produce or accomplish. If there is more than one
resource assigned to it it implies they are all working together as a unit,
a team. If they have to produce more than originally planned for, the whole
team will have an increase in the amount of work required. If it's
otherwise, as your post suggests, what you have described as one task is
really at least two and more likely more than that. The problem you're
facing is caused by not breaking down your work breakdown structure far
enough - it should be decomposed to the level of 1 resource=1 task. When
you do, the problem of rebaselining one resource's work goes away and it
becomes an extremely simple exercise.
 

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