Review development process
The development process defines the worker roles and the useful ways in which the roles can be defined to create teams.
This reviews your process documentation for guidance. |
Review schedule
The schedule identifies which tasks need to be performed and the resources (personnel) assigned to them. |
Determine key roles
The key roles are the ones that have the most profound impact (negative or positive) on project success. This can vary to a
degree based on the work items to be used in the project. In most cases, the architect and project leader are key roles.
Other key roles can be determined from the risk management plan. |
Evaluate personnel for strenghts and weaknesses
Projects that treat workers as interchangeable are far less efficient than ones that take advantage of workers’ individual
strengths, weaknesses, and interests. Not every one has the skill to solve partial differential equations, construct an
algorithm, or write a device driver in an assembly language. To be effective, you must assign roles on the basis of
ability. |
Assign personnel to key roles
The key roles have the most impact to the success of the project, so, in general, you will take great care in the
assignment of workers to these roles. |
Evaluate proposed team structure in terms of schedule
The team structure is formed to support the delivery of the product within the cost and schedule constraints. This step is
focused on ensuring that you've done the best job of creating the project roles and filling them with the most appropriate
staff. This step includes consideration of the schedule and resource availability constraints. |
Create and publish the team organization chart
It is important that your team structure is known and easily accessible by all of the team members. |
|