S
Shane
We are trying to use Team Resources in doing resource management. The
steps leading up to the reassignment step are as follows:
- Build the project team with the required Team Resources.
- Assign Team Resources to tasks.
- Publish the schedule
We make the team lead the default assignment owner for each team
resource. When the schedule gets published, the team lead gets an
email and the task(s) show in his/her task list.
Since the only resources found on the project's team are team
resources, in order to assign work to an actual person, the team lead
must first add that individual to the project's team. To do that here
are the steps:
- Open the project in PWA
- Click on Build Team
- Assign the individual to the project's team
- Click Save
Here's the kicker. Now when the team lead goes to his/her task list
and attempts to reassign a task to the newly added resource, that
resource doesn't yet show in the drop-down list. It appears that the
project still needs to be "published" by the project's owner before
the resource will officially appear in the project's team.
My question is "are we doing this correctly"? It appears that the step
where the project's owner needs to publish the schedule before the
team lead can reassign the task is adding complexity to the process
that we just don't need. In my opinion, the team lead should be able
to add the resource to the project's team and then immediately be able
to reassign a task to that resource and not have to wait for the
project owner to publish the schedule. Even better, the team lead
should be able to reassign the task to member of the team and that
person is automatically added to the project's team.
steps leading up to the reassignment step are as follows:
- Build the project team with the required Team Resources.
- Assign Team Resources to tasks.
- Publish the schedule
We make the team lead the default assignment owner for each team
resource. When the schedule gets published, the team lead gets an
email and the task(s) show in his/her task list.
Since the only resources found on the project's team are team
resources, in order to assign work to an actual person, the team lead
must first add that individual to the project's team. To do that here
are the steps:
- Open the project in PWA
- Click on Build Team
- Assign the individual to the project's team
- Click Save
Here's the kicker. Now when the team lead goes to his/her task list
and attempts to reassign a task to the newly added resource, that
resource doesn't yet show in the drop-down list. It appears that the
project still needs to be "published" by the project's owner before
the resource will officially appear in the project's team.
My question is "are we doing this correctly"? It appears that the step
where the project's owner needs to publish the schedule before the
team lead can reassign the task is adding complexity to the process
that we just don't need. In my opinion, the team lead should be able
to add the resource to the project's team and then immediately be able
to reassign a task to that resource and not have to wait for the
project owner to publish the schedule. Even better, the team lead
should be able to reassign the task to member of the team and that
person is automatically added to the project's team.