One resource per task?

Home Forums Discussion Forum One resource per task?

Tagged: , ,

Viewing 4 reply threads
  • Author
    Posts
    • #5023
      Ricardo Rangel
      Keymaster
      Just got my MPUG Microsoft Project 2010: Desk reference guide. While perusing the pages a note jumped out and has caused some confusion. The guide states that in project assign only one resource to a task. If needed break the task into subtasks to assign more then one resource.
      Went looking through some other books and see no mention of this. Does anyone understand why this would be helpful?
    • #6511
      Ricardo Rangel
      Keymaster
      Jason, where are you reading that in the guide? (Page and section)
    • #3932
      Ricardo Rangel
      Keymaster
      You can assign multiple resources to a task without a problem.  Many users are not aware of the effort-driven flag that is set for each task.  If the flag is turned on, the task will get shorter in duration as each resource is added.  For this reason some people feel that only one resource should be assigned per task.  Turning off the flag per task will resolve this issue. (Double click on the task –> advanced tab –> removed the effort-driven check mark).
      I have worked with clients who have assigned 100+ resources to a task.   Go ahead and assign as many as you need without concern.
      I also would like to know where you saw this because it should be corrected if possible.
      Thanks.
    • #6518
      Ricardo Rangel
      Keymaster
      In the MPUG Microsoft Project 2010: Desk refernece guide.  On page 3 in the "Working with resources" section.  Just under entry 4, threre is a tip that reads "Tip:  In Microsoft Project, assign only one resource to a task.  Break tasks into subtasks in order to allocate it to more than one resource."

    • #6822
      Ricardo Rangel
      Keymaster

      Bringing up a good old question.  I agree with all that you can assign more than one resource per task.  You certainly don’t want to create multiple tasks in order to emulate the need.  I suspect what it was trying to communicate (as a best practice) is that the more people you assign to multiple tasks, and harder it is to manage overall resource utilization.  It is much easier to arrange tasks with a single assigned resource in order to manage overallocation than it is to manage many tasks with multiple assignments.  That is one of the concepts to consider when initially creating and assigning the WBS.  But, it is only one of many considerations and not ever an absolute.

Viewing 4 reply threads
  • You must be logged in to reply to this topic.