A
Angel
Need some ideas on best practices for reassigning resources.
Scenario:
Plan has been created, resources assigned, baselined and published.
Then for whatever reason, some of the assignments need to be changed to a
different resource. Not ALL assignments need to be changed so the Build Team
From Enterpise & Replace feature is not a viable option.
My method for changing assignments has always been to assign the new
resource to the task without rebaselining. I assign work but don't rebaseline
so baseline work=0 for new resource. Then I ask the original resource to
simply zero out the remaining work or reject the tasks they are no longer
going to work on. The problem with this method now is that we are using
baseline work as a factor in our availability reports so if i don't
rebaseline the task (NOT a best practice in my book), the data in the
availability reports won't show up correctly.
If I simply replace the original named resource with the new resource and
republish the assignment, the original task stays on the user's PWA timesheet
with an X next to it... and I'm not quite sure what happens if they had
actual work against that task. For the sake of reporting availability
accurately, if the actual work stays in the plan, simply replacing the
resource may be the best method... In which case I'll just have to do lots of
training on how and when to use the "hide" button to get rid of those deleted
assignments.
Ideas, suggestions???
Thanks!
Scenario:
Plan has been created, resources assigned, baselined and published.
Then for whatever reason, some of the assignments need to be changed to a
different resource. Not ALL assignments need to be changed so the Build Team
From Enterpise & Replace feature is not a viable option.
My method for changing assignments has always been to assign the new
resource to the task without rebaselining. I assign work but don't rebaseline
so baseline work=0 for new resource. Then I ask the original resource to
simply zero out the remaining work or reject the tasks they are no longer
going to work on. The problem with this method now is that we are using
baseline work as a factor in our availability reports so if i don't
rebaseline the task (NOT a best practice in my book), the data in the
availability reports won't show up correctly.
If I simply replace the original named resource with the new resource and
republish the assignment, the original task stays on the user's PWA timesheet
with an X next to it... and I'm not quite sure what happens if they had
actual work against that task. For the sake of reporting availability
accurately, if the actual work stays in the plan, simply replacing the
resource may be the best method... In which case I'll just have to do lots of
training on how and when to use the "hide" button to get rid of those deleted
assignments.
Ideas, suggestions???
Thanks!