C
Cole
All,
Let me preface this question with I agree with you I'm trying to
convince others on NOT assigning resources at the summary level.
In my search to list all the concerns and issues with regarding
assigning resources at the summary level I've found:
1. Resource Loading will be inaccurate as work will lengthen at the
Summary Level as the tasks below move around (regardless of whether
they are being worked on or not).
2. In addition when sub-tasks overlap or when there is a gap between
the tasks work is not the same in both cases.
3. Assigning a resource to a summary task is equivalent to assigning
it to each of the sub-tasks - and it isn't, it will produce work
according to the duration of the summary task and we all know that is
not necessarily equal to the sum of the durations of the sub-tasks
4. A Summary Line isn't really a task, rather, it is simply a top
level summary of the sub-tasks under
it. Resource assignments on a Summary Line also can cause some
unexpected results.
5. When a resource is assigned to both a summary task and one of the
sub-tasks, and the sum of assignment units exceeds the max units of
the resource, leveling cannot solve the overallocation.
6. People forget about it and then start complaining Project "doesn't
calculate correctly". Indeed, once you
assign a resource to the summary task, Work and Cost on that summary
task
are no linger the total of the sub-task.
7. Assigning resources to summary tasks can cause obscure double
booking with data confusion, and thus should be avoided entirely.
Am I missing any other reason?
Cole
Let me preface this question with I agree with you I'm trying to
convince others on NOT assigning resources at the summary level.
In my search to list all the concerns and issues with regarding
assigning resources at the summary level I've found:
1. Resource Loading will be inaccurate as work will lengthen at the
Summary Level as the tasks below move around (regardless of whether
they are being worked on or not).
2. In addition when sub-tasks overlap or when there is a gap between
the tasks work is not the same in both cases.
3. Assigning a resource to a summary task is equivalent to assigning
it to each of the sub-tasks - and it isn't, it will produce work
according to the duration of the summary task and we all know that is
not necessarily equal to the sum of the durations of the sub-tasks
4. A Summary Line isn't really a task, rather, it is simply a top
level summary of the sub-tasks under
it. Resource assignments on a Summary Line also can cause some
unexpected results.
5. When a resource is assigned to both a summary task and one of the
sub-tasks, and the sum of assignment units exceeds the max units of
the resource, leveling cannot solve the overallocation.
6. People forget about it and then start complaining Project "doesn't
calculate correctly". Indeed, once you
assign a resource to the summary task, Work and Cost on that summary
task
are no linger the total of the sub-task.
7. Assigning resources to summary tasks can cause obscure double
booking with data confusion, and thus should be avoided entirely.
Am I missing any other reason?
Cole