Summary Resource Assignment in standalone MS Project File
in [Project]
|
From: Cole on 19 Mar 2010 11:47 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
From: Trevor Rabey on 19 Mar 2010 20:20 How many reasons do you need? Just don't do it. Do you have even one reason for doing it, other than laziness and misunderstanding? -- Trevor Rabey 0407213955 61 8 92727485 PERFECT PROJECT PLANNING www.perfectproject.com.au "Cole" <beyondnikao(a)gmail.com> wrote in message news:0ae0eea0-d0b6-46eb-9ea6-aa6ba4c11d01(a)r27g2000yqn.googlegroups.com... > 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
From: Rob Schneider on 20 Mar 2010 05:50 I think there is a missing feature in Project that detects when resources are assigned to a summary task and then throws up a warning message. --rms www.rmschneider.com On 19/03/10 15:47, Cole wrote: > 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
From: Mike Glen on 20 Mar 2010 05:26 I took Cole's post to be something he can use to give reasons to people in his organisation who want to do so. I took it as a training issue to give reasons why it should not be done. Mike Glen Project MVP "Trevor Rabey" <trevorATperfectproject.com.au> wrote in message news:ovydnf7Hbrzw6znWnZ2dnUVZ8judnZ2d(a)westnet.com.au... How many reasons do you need? Just don't do it. Do you have even one reason for doing it, other than laziness and misunderstanding? -- Trevor Rabey 0407213955 61 8 92727485 PERFECT PROJECT PLANNING www.perfectproject.com.au "Cole" <beyondnikao(a)gmail.com> wrote in message news:0ae0eea0-d0b6-46eb-9ea6-aa6ba4c11d01(a)r27g2000yqn.googlegroups.com... > 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
From: Ismet Kocaman on 20 Mar 2010 19:43
There will be no assignments on summary tasks, that's for sure. The below paragraph is from the help pages. Notes -You can assign a resource to a summary task. This is useful, for example, if the resource is responsible for a group of tasks. -If the resource's time on the group of tasks stays the same regardless of how the total duration of the subtasks changes, then the resource should be assigned to the individual subtasks, and not to the summary task. -If you assign a resource full time to a summary task, don't also assign the same resource full time to subtasks under that summary task, or you may cause unnecessary overallocations . Ref. http://office.microsoft.com/en-us/project/HA101935931033.aspx I tried to think of an example case where the above statement applies but I couldn't be able to create a useful one. I would really appreciate your feedback on that case. Regards, Ismet Kocaman "Rob Schneider" wrote: > I think there is a missing feature in Project that detects when > resources are assigned to a summary task and then throws up a warning > message. > > > --rms > > www.rmschneider.com > > > > > On 19/03/10 15:47, Cole wrote: > > 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 > . > |