"A team effort is a lot of
people doing what I say." (Michael Winner)...but seriously...
Structuring the Intranet Project Team
The following short passage from the book "Empowered Teams" (Wellins, Byham
& Wilson) puts it very well:
"Highly effective teams are composed of groups of committed individuals who trust each other; have a clear sense or purpose about their work; are effective communicators within and outside the team; make sure everyone in the team is involved in decisions affecting the group; and follow
a process that helps them plan, make decisions, and ensure the quality of their work"
A clear sense of purpose for the team
It is important to create meaningful workstreams for projects, shaped around
the particular scope you are delivering and your way of working. The four "orientational" streams in the diagram above (blue boxes) are a good generic starting point for discussion;
Suggested Project Team Structure
The purpose of Solutions Development is to build the
platform and applications, test it and ready it for implementation (up to & including pre-live staging). Skill sets include architects, developers and testers.
The purpose of Service Delivery is to accept the unit-tested system into live service and then support it in
In this example, it is assumed that the project's development activity is largely or wholly outsourced and there is thus a Commercial Stream, charged with managing the third parties
contracted to the project.
Finally (but by no means least) is the Business Readiness team, who manage the change into the business.
Help the team to follow a process
The structure of the team will (largely) be driven by the processes being
used on the project (i.e. project management and
development methodology being used). The team above assumes a mostly waterfall development
methodology. This is the method most likely to be appropriate for an intranet portal project, where large scale, wholly new infrastructure elements are being built (as a major part of the project).
However, once the infrastructure is in, it may be more appropriate (e.g. for later stages or follow-on projects) to re-build the project team around a Rapid Application Development methodology
(where workstreams are dedicated to particular applications, with multi-skilled teams of architects, developers, implementers and business people all working together).
Ensure Quality in the work of the team
The inclusion of a separate project assurance group helps to ensure that the
team's products are being adequately quality controlled (this reduces problems and rework later).