locked
Team Assignments Question RRS feed

  • Question

  • I've gotten what appears to be some conflicting information regarding team resources.  I figured before I got too heavily invested in experiments, I'd ask you wonderful folks. :)

    I've read a few articles regarding team assignments AND I have the Orange and Blue MSPE books.

    The MSPE books and two of the articles (also MSPE) say to set up the Team Resource as a generic resource, and check the Team Assignment Pool checkbox for that resource.  However, the other two articles I've read, which I'll list here, suggest otherwise:
    http://office.microsoft.com/en-us/project-server-help/assign-work-to-a-team-HA010242141.aspx
    http://evildoctorporkchop.spaces.live.com/blog/cns!88E61D218103A246!620.entry?sa=894299011
    These articles say to create the resource as as a regular resource (non-generic) and assign a "Team Leader" by setting the Default Assignment Owner.  This sounds like what I was thinking would be a better option.

    It looks like both methods would be functionally correct, so can anyone out there maybe tell me what the pros vs. cons would be for going one way or the other?  It looks like the difference between the two methods would be that the tasks would show up in either the PM's task page (MSPE method) or the Default Assignment Owner's task page (other method).  Is that it?

    Friday, August 20, 2010 7:46 PM

Answers

  • Kevin --
     
    Good question.  Either approach will work.  It all depends what you want to do with team resources and team assignments.  Our books and our FAQ take one approach.  The articles you quote offer an alternative.  Both are right, and both should work fine for you.  Do remember this, however:  you use team assignments in an environment where you want to assign a group of resources to a task AND where you want one of the resources to take over the task and do the work.  This is NOT the way to assign a team of resources to a task and have every one of them work on the task.  Hope this helps.

    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    Friday, August 20, 2010 9:17 PM

All replies

  • Kevin --
     
    Good question.  Either approach will work.  It all depends what you want to do with team resources and team assignments.  Our books and our FAQ take one approach.  The articles you quote offer an alternative.  Both are right, and both should work fine for you.  Do remember this, however:  you use team assignments in an environment where you want to assign a group of resources to a task AND where you want one of the resources to take over the task and do the work.  This is NOT the way to assign a team of resources to a task and have every one of them work on the task.  Hope this helps.

    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    Friday, August 20, 2010 9:17 PM
  • As always, thanks so much for your help.  This is exactly what I was hoping for.  The idea is that the person putting the schedule together will know which team will be working on a task, but not necessarily which person.  I think this is perfect.

    Friday, August 20, 2010 9:41 PM
  • Kevin --
     
    I am glad that team assignments will work for you!  Yippee!!  And you are more than welcome for the help, my friend.

    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    Saturday, August 21, 2010 1:21 AM
  • Hi,

    I just wanted to clarify this, if I create resources as teams and assign these teams to the tasks. Then when a new employee comes into the organization, I just add them to the team and hence the employee is assigned to all the projects that the team was assigned to. Would this work fine?

    Do I need to publish the projects again or anything like that or just adding the employee to the team is enough?

    Thanks

    Sunday, September 25, 2016 3:58 AM
  • feryall --

    No, this is NOT how team resources work.  When you assign a team resource to a task, this means that only ONE of the team members associated with that team resource will be able to self-assign the task to him/herself.  This is NOT how to assign a group of people to a task simultaneously.  Hope this helps.


    Dale A. Howard [MVP]

    Sunday, September 25, 2016 5:07 PM
  • Hi Dale, Thanks a lot for clearing that up.

    So how would you achieve what I'm trying to achieve?

    i.e. if I want to assign a group of people to a project and don't want to add a new member to all 100 projects. I want to be able to add a new member to a group/team and he should be able to enter his time for any of the projects that group/team has been delegated to without me having to publish all the projects.

    Regards

    Monday, September 26, 2016 7:50 PM
  • feryaal --

    There is no easy way to do this.  At the minimum, you will need to open every project and add the resource to the project team.  You will also need to assign the new team member to tasks as well.  Team resources simply do not offer you the functionality you seek.  Sorry.  Hope this helps.


    Dale A. Howard [MVP]

    Tuesday, September 27, 2016 12:38 PM