ORGANIZATIONAL STRUCTURE FOR THE PROJECT
The way a project team is structured can play a major role in how it functions. Different styles of team will have different characteristics. For example, do we wish to encourage discussion with the business representatives or to keep them at arm's length so the developers can make good progress? Careful consideration of team composition and reporting relationships can make a big difference to the results.
The various roles in the team will depend on the nature of the project. As well as the main team roles, consider the other participants and how they fit into the picture.
Project roles and resources will have been identified as part of the planning, estimating and resourcing process. STYLES OF TEAM
There are two main structural dimensions to the project team:
* What type of resource? * What are they delivering?
For example, a website designer may be working with business managers and network specialists to create a storefront whilst another website designer is working with different business managers but maybe the same network specialist on an Intranet application for presenting internal management information on sales - both as part of the same project. So, does it make sense to have a team of developers, a team of managers and a team of network specialists, or should we have a team for the storefront and a team for the management information system?
Rather than seeing this as an "either or" choice, we could think of the project team as a matrix. Members of the various resource type teams will need to work together to share knowledge and ensure a consistent solution. People working together on the various processes or functional aspects of the solution will equally need to work together.
Each of these sub-teams, whether horizontal or vertical, will need a recognized leader. Team members will need to understand their individual roles
ROLES AND RESPONSIBILITY
There are many