Guide
The project team: roles, structure and how to build it
Whatever method you follow, it is the project team that carries a project to completion — provided its roles and its availability are real.
Without a strong and capable project team, project management techniques are useless. Whichever approach you choose, it is the team that brings a project to a successful finish. Building one is not a matter of collecting available people: it is a matter of covering the roles the project needs, with enough time genuinely secured for each of them.
Roles, not just names
A team is built from roles: sponsor, project manager, business owners, technical contributors, quality and support. Naming the role before the person avoids the classic trap of a project staffed by whoever happened to be available. It also reveals gaps early — a project with no identified business owner will discover the consequence at acceptance, not before.
The core team and the extended team
A useful distinction: the core team works on the project continuously and is accountable for the deliverables; the extended team contributes at specific points — legal review, security assessment, a supplier, an architect. Both belong in the plan, but only the core team should be in every meeting. Confusing the two produces either an unmanageable meeting or a forgotten contributor.
Availability is part of the commitment
A contributor allocated “20% of the time” without that being reflected in their other assignments is not really allocated. Consolidating each person’s workload across all their projects is the only way to know whether the team you drew on paper actually exists. In most organizations the scarce resource is not headcount but the specific skill that three projects need in the same quarter.
Clarifying who decides what
Most project friction is not technical: it comes from an unstated split between who does the work, who is accountable for it, who must be consulted and who merely needs to be informed. Writing that down once, in a RACI matrix or a simpler equivalent, costs an hour and removes an entire category of recurring argument.
Bringing the team together
A kick-off meeting is not ceremony. It is where the objective, the deliverables, the roles and the ground rules are stated in front of everyone at the same time, so that nobody works for three weeks on a different understanding. Teams that skip it usually pay for it around the first milestone.
Keeping the team informed
FoxPlan gives each member a personal view of their tasks and cards across projects, with notifications on assignments and comments — so the team stays synchronised without a weekly status meeting whose only purpose is to relay information. The consolidated workload view shows, before you commit, whether the people you intend to name are actually free.
