Multiple Resources Putting in Different # Hours on a Task
Multiple Resources Putting in Different # Hours on a Task
(OP)
Is there a way to designate different numbers of hours that individual resources should contribute to a task? I don't want to change the % of a resources time spent on a task, but rather the number of hours each resource puts in to a task that has multiple resources assigned to it.
For example, consider a task with an amount of work set at 20 hours to complete. I want resource A to spend 10 hours on the task, and resource B to spend 7 hours, and Resource C to spend 3 hours each on this task. How can I set up this scenario in Project?
Thank you in advance for your help!
For example, consider a task with an amount of work set at 20 hours to complete. I want resource A to spend 10 hours on the task, and resource B to spend 7 hours, and Resource C to spend 3 hours each on this task. How can I set up this scenario in Project?
Thank you in advance for your help!





RE: Multiple Resources Putting in Different # Hours on a Task
TTFN
RE: Multiple Resources Putting in Different # Hours on a Task
1. I thought percentages represented the % of a resource's time that can be devoted to a task, which isn't necessarily representative of the amount of time you expect them to devote to a given task. Could this become a problem if you have a longer duration for a task because other resources are expected to put in more time for example?
2. Is there any way to divide work on a task between resources by assigning each of them a number of man-hours they're expected to devote to the task? This is just more intuitive to me than percentages.
Thanks again for the help!
RE: Multiple Resources Putting in Different # Hours on a Task
As far as I know, percentage is the only way to load resources.
General comment. Good practice dictates that your tasks shouldn't be long to begin with. It makes it extremely difficult to track and monitor, and you'll have to wait a very long time to find out that you're behind schedule. A typical task structure should be broken up into 2-4 wk tasks with measureable milestones, ideally 2 wk. This ensures that your status is never more than 2 wks stale.
TTFN