Skip to content
Skip to main content

About this free course

Become an OU student

Download this course

Share this free course

How teams work
How teams work

Start this free course now. Just create an account and sign in. Enrol and complete the course for a free statement of participation or digital badge if available.

1.1.1 Project teams in practice

In reality, few teams are exactly as described in the previous section and they are usually some hybrid or mixture of these basic forms. For example, an operational team may be a permanent part of an organisation‘s structure – a top management team or a team running a helpdesk. Or the team may be temporary, such as a project team set up to introduce a new piece of software into an organisation. Some authors note that there is a spectrum of team organisation structures from functional through matrix and on to a project or single team structure. The different structures for project teams have different advantages and disadvantages so that one team structure may suit a particular task in some organisations better than another.

Table 1 sets out the strengths and weaknesses of different team structures. Note that in this table, we are defining a client to be a person or organisation that requested or receives the product of the team’s work.

Show description|Hide description

Table 1 description.

The table has two columns. The headings are ‘Strengths’ and ‘Weaknesses’.

Under these headings there are three rows.

The first row is a ‘Functional team’. The strengths of a functional team are: handles routine work well; line management has control of projects; pools technical and professional expertise. The weaknesses of a functional team are: communication and coordination across functional areas in an organisation is more difficult; can be inflexible; tends to push decision making upwards.

The second row is a ‘Matrix team’. The strengths of a matrix team are: acceptable to traditional managers; top management retains control of projects but are relieved of day-to-day decisions; flexibility in the personnel assigned. The weaknesses are: project staff have dual reporting lines, which can cause conflicts of priorities; staff appraisal and performance measurement is difficult; the team leader may not be able to influence who is assigned to the project.

Finally, the third row describes a ‘Contract team’. The strengths of a contract team are: easy to employ technical and professional expertise; reduces training requirements for the client; the team can use its own management structure; can be used to bring a number of organisations together. The weaknesses of a contract team are: difficult for the client to assess the quality of the work and progress of the project; there may be problems on acceptance as the client is the judge of project success; difficult to identify and resolve political or organisational issues; communication between geographically remote team members is difficult.

Table 1 Some strengths and weaknesses of different structures for project teams
StrengthsWeaknesses
Functional teamHandles routine work well. Line management has control of projects. Pools technical and professional expertise.Communication and coordination across functional areas in an organisation is more difficult. Can be inflexible. Tends to push decision making upwards.
Matrix teamAcceptable to traditional managers. Top management retains control of projects but are relieved of day-to-day decisions. Flexibility in the personnel assigned.Project staff have dual reporting lines, which can cause conflicts of priorities. Staff appraisal and performance measurement is difficult. The team leader may not be able to influence who is assigned to the project.
Contract teamEasy to employ technical and professional expertise. Reduces training requirements for the client. The team can use its own management structure. Can be used to bring a number of organisations together.Difficult for the client to assess the quality of the work and progress of the project. There may be problems on acceptance as the client is the judge of project success. Difficult to identify and resolve political or organisational issues. Communication between geographically remote team members is difficult.
(The Open University, 2008)