Please login or join to subscribe to this thread
Here's a few examples from the template library:
Can you explain a little bit? What is your problem, specifically?
what else included in the project team assignments (as part of acquire resources), there is no detailed description in the PMBOk for the better understanding.
At a bare minimum, it would specify the team member and what activities or deliverables they are responsible for.
the assignment itself is an action to map real people (warm bodies) to roles (cold bodies) on the project. It is documented in a team directory (lists all people on the team) in that each name is assigned to one or more roles. You may also put real names in the boxes of the orgchart. Which triggers changes to the orgchart if people change.
Besides assignment to roles, you can assign people to tasks, which is more granular (there are more tasks than roles) and may take place every week in a project.
If you assign an individual to a role, they might not have all the defined skills and capabilities (as we often over-specify a role) as defined in roles&responsibilities, and we might want to split and shift responsibilities after we see who is the guy.
So, the assignment action may result in changes to the resource plan.
Also, an individual comes with their own resource calender, which might influence the schedule.
So, besides assigning a human to a role, it may trigger changes to already planned items.
Even for assigning an individual, you would like to have a specific skillset, negotiations will play a key role here
Please login or join to reply