PS07 - Teams

[TroyS]

I created some generic team resources in PWA and assigned them to Teams.
For example: Team - IT, Team - Finance, Team - Legal

I've set up a project with tasks and assigned the appropriate Team to the task

My Goal/Scenario: Those resources who are in the appropriate Team will be
able to self-assign themselves to the task in My Task and update Actual Work
when they need to.

Will this work: Having multiple Resources from the Team assign themselves
whenever they need to use the task? OR am i going to run into approval
contention when Resource One assigns themselves to the task and Resource Two
(same Team) assigns themselves to the same task?

However, I thinking this won't work because it appears to only work for one
Resource from the Team to do this ...I'm thinking if a 2nd person on the same
Team assigns themselves and wants to add Actual Work, that approvals won't
flow properly? Is this a 'hot-potato' scenario where only 1 Resource at a
time can assign themselves to a Team Task?

Guidance is appreciated

 

[TroyS]

as a followup to my own...
I as admin see all of the Tasks for each of the Teams assigned in My Tasks.
Because i assigned multiple teams to tasks, i see many pages of tasks / Team
combinations.

For example, I assigned to Task A, 4 different Teams as individuals across
those teams may need to use Task A once in awhile....So when i go to My
Tasks, I see Task A repeated 4x for each Team Name...is this going to happen
to 'regular' users vs an Administrator?

Is this behavior due to me being my own Timesheet Manager?

Is this going to be true for 'regular' users even though they are not in all
Teams but only 1 specific team? If a person in a particular team can see all
published tasks from a project including those tasks where they are not in
that particular team, then this provides a sorting/filtering problem and I
don't see any extensive filtering in My Tasks.

 

[Gary L. Chefetz [MVP]]

One person at a time can assign himself to a task. It sounds as though you
are confusing the purpose of team tasks with the purpose of Administrative
time. Team tasks are good for tasks in a project that anyone on a certain
team can perform as pick-up work. This type of work should be shareable by
nature. For instance, consider the task of cutting and crimping 250 patch
cords for a datacenter installation. Anyone on the network team can work on
this when they have time available. In this case a user might spend an hour
making and testing a couple dozen patch cords, go back to his desk,
self-assign a team task, enter the update on the task and then pass the
remaining work back to the team.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

 

[TroyS]

Thx for the info.
Just to confirm, it sounds as if team assignments is really suppose to be a
'one-person-can-use-at-a-time' type of usage....

any suggestions around how to come up with an alternative to administrative
projects in 2003? I liked the idea of being able to have calendar year based
admin projects with related tasks (ie Vacation 2007, Sick Time 2007, etc) ...

I have several hunded cost centers that someone could, in theory, charge
time to ...i' don't want to necessarily list it in the admin tasks even
though i could choose not to display them...

any ideas beyond listing in admin tasks?

 

[Gary L. Chefetz [MVP]]

Troy:

By design, the Admin tasks are where this should go. You can always create
Admin-like plans in 2007 following the guidance we provide on
projectserverexperts.com, however this is not a perfect solution.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com