Resource Groups

[wclairmont]

I have a project that has about 1000 resources spread across the country. To
assign up to 50 resources to a task is starting to get tedious.

Is there way to create resource groups that would allow me to assign
multiple resources to a task by assigning a predefined custom resource
grouping?
i.e
----- Marketing (group)
---------- Bob Smith (resource)
---------- Trevor Play (resource)
---------- John Howard (resource)
----- Development (group)
---------- Terry Barr (resource)
---------- Donald Trump (resource)
---------- Wendy Mohl (resource)

When I assign Marketing (group) to a task, Project knows that I have assign
the 3 associated resources to the task, as they have dfferent rates, and
other unique resource information.

If anyone could lend a hand that would be great.

Thanks, Wade

 

[John]

I have a project that has about 1000 resources spread across the country. To
assign up to 50 resources to a task is starting to get tedious.

Is there way to create resource groups that would allow me to assign
multiple resources to a task by assigning a predefined custom resource
grouping?
i.e
----- Marketing (group)
---------- Bob Smith (resource)
---------- Trevor Play (resource)
---------- John Howard (resource)
----- Development (group)
---------- Terry Barr (resource)
---------- Donald Trump (resource)
---------- Wendy Mohl (resource)

When I assign Marketing (group) to a task, Project knows that I have assign
the 3 associated resources to the task, as they have dfferent rates, and
other unique resource information.

If anyone could lend a hand that would be great.

Thanks, Wade

Wade,
Project has the ability to set up resource groups but the members of the
group must all be of the same labor type (i.e. have the same pay rate).
And that makes sense since resources are grouped because the individual
members are more-or-less interchangeable, skill wise.

It sounds like your tasks are way to broad in scope if you are assigning
up to 50 individual resources per task. In my opinion, 10 resources is
about the max and the norm is 5 or less. I suggest you re-structure your
plan to break the tasks into more definitive pieces. Then you won't have
an issue with multiple resource assignments per task. If the overall
project plan is also very large (i.e. greater than a 5000 tasks), I
would also suggest the plan be broken into separate subprojects. Those
subprojects can be inserted into a master to get the complete picture.

Hope this helps.
John
Project MVP

 

[Steve House [Project MVP]]

Adding to John's comment, I teach my classes that when you do the task
breakdown you try to take it down to the level of granularity where a task
equates to the work done by one resource - defined here as a skill set
package, ie, a person or a team that works together as a unit like perhaps a
surgical team - that results in a single tangible deliverable. 50 people is
a mighty big team! Also give some attention to the "8/80" rule of thumb.
Tasks requiring more than 80 hours are probably not detailed sufficiently to
effectively manage while tasks under 8 man-hours indicate you're
micromanaging to excess.