What Are the Key Roles in a Project Team for IT Projects?

A manufacturer in the Beauce region launches its ERP implementation. The VP Finance “sponsors” the project but attends no steering committee. The IT director manages, designs and tests at the same time. Six months later, nobody knows who approved the scope or who speaks for the warehouse users. The problem is not the software: it is the roles.

Figures cited here come from public studies (Gartner, PMI, Panorama Consulting) and describe market trends, not the situation of your project.

According to Gartner, more than 70% of recently implemented ERP initiatives will fail to fully meet their original business case goals by 2027, and as many as 25% will fail catastrophically, most often for lack of executive team commitment.

What are the key roles in a project team and why define them?

An IT project team rests on nine key roles: the sponsor, the project director, the PCO, the solution architect, the business analyst, the software package expert, the developer, the infrastructure lead and the change management lead. A role is defined by its tasks and responsibilities, not by a job title. One person can hold several, provided each one is named and owned.

Defining roles is not a bureaucratic exercise. Gartner lists unclear division of responsibilities among the direct causes of delays, scope deviation and budget overruns. A role with no owner is a decision nobody makes.

The benchmarks worth remembering:

• According to Gartner, 75% of ERP strategies are not strongly aligned with overall business strategy, which feeds confusion and lacklustre results.
• According to PMI's Pulse of the Profession 2025 (2,254 project professionals surveyed), only 18% of project professionals demonstrate high business acumen; they meet business goals 83% of the time versus 78%, and stay on budget 73% of the time versus 66%.
• Also according to PMI (2025), 96% of respondents rate stakeholder management as important or very important, the most consensual skill in the survey.
• According to Panorama Consulting's 2026 ERP Report, more than a quarter of organizations exceeded their budget, with unexpected technology needs as the leading cause.

Who governs the project: the sponsor, the project director and the PCO?

Three roles provide governance: the sponsor, who secures resources and answers for the benefits; the project director, who delivers the solution within scope, schedule and budget; and the PCO, who keeps the management processes alive and prepares the reporting. When one of the three is missing, the other two compensate poorly.

The sponsor. They obtain the human, material and financial resources from the organization and act as the project's ambassador to senior management. They take part in major decisions, champion the transformations and remain accountable for delivering the expected benefits. They use their internal relationships to clear political obstacles. A sponsor who delegates their seat at the steering committee is no longer a sponsor.

The project director. They answer for the delivery of the new solution. They lead work planning and estimates, ensure scope, schedule and budget are respected, set up the required management processes and report progress to the sponsor.

The PCO (project control officer). They make sure the management processes are actually applied: tracking hours, risks, changes and deliverables. They help the project director produce reliable reporting. On a project above 5,000 hours, this role frees the project director for what matters: decisions.

Who designs the solution: the architect, the business analyst and the software package expert?

Three roles design the solution: the solution architect, who provides technical leadership and integration; the business analyst, who masters the needs and represents the project's “customers”; and the software package expert, who resolves the fit between needs and the software's features. Their daily dialogue prevents costly customizations.

The solution architect. They make sure no component is missing (business solution, ERP, specialized modules), design integrations with existing systems, validate data flows and review major data structures. They confirm the implementation approach is sound and guide the team's understanding of the solution. The role of the solutions architect in 2026 goes far beyond technical expertise.

The business analyst. They master the business needs the project must satisfy, design the new processes with the software package expert, select the best practices to build in and take an active part in testing. They work with process owners until the solution is accepted. We detail the role of the business analyst in IT projects in a separate article.

The software package expert. They work with business experts to match needs and features, configure the applications and support solution validation. They bring the product expertise without which the project reinvents what the software already does.

Who builds and deploys: the developer, the infrastructure lead and the change management lead?

Three roles build and deploy: the developer, who programs conversions, interfaces, reports and adaptations; the infrastructure lead, who turns needs into working servers, network and software; and the change management lead, who prepares the organization to adopt the new processes. The third is almost always the first one cut.

The developer. They prepare the programs that import data into the new system, build the interfaces with existing applications, program the missing reports and carry out the adaptations required by the organization's specifics. Every adaptation must be justified: changes to software packages remain a very expensive habit.

The infrastructure lead. They analyze the needs to translate them into an adequate infrastructure solution, install servers, network, software and peripherals, and guarantee the infrastructure runs properly throughout the project, including test environments.

The change management lead. They set out the communication, training and organizational development strategies needed for the new business processes to be adopted. They accelerate the maturation of the project team itself. Gartner ranks low end-user adoption among the main causes of ERP failure; change management is much more than a communication plan.

A role with no owner is a decision nobody makes and an invoice everybody pays.

How do you scale these roles to the size of your project?

The nine roles stay relevant whatever the project size, but their intensity varies: an 80-employee SME will often give several roles to one person, while a multi-site project needs a full-time owner for each. Other roles get added depending on the nature of the project and the organization's culture: data lead, test lead, process owners.

The rule does not change: every role has a name, a person and reserved time, written into the project charter before kickoff.

Frequently asked questions

What is the difference between the sponsor and the project director?

The sponsor answers for business benefits and provides the resources: they sit on the leadership team, settle major decisions and clear political obstacles. The project director answers for delivery: scope, schedule, budget and management processes. The first decides why and with what means; the second organizes how and reports to the first at every milestone.

What is a PCO in a project team?

The PCO (project control officer) makes sure the planned management processes are actually applied: tracking hours, costs, risks, change requests and deliverables. They prepare the dashboards and help the project director produce reliable reporting for the steering committee. On large projects, this role keeps the director focused on decisions rather than spreadsheets.

Can one person hold several roles?

Yes, and it is common in SMEs. A business analyst can also act as software package expert, an IT director as infrastructure lead. Two combinations are risky, though: sponsor and project director, because nobody watches delivery anymore, and project director and change management, because adoption always comes second when deadlines get tight.

Why name a change management lead from the start?

Because adoption is decided during the project, not after. Gartner cites low end-user adoption and lack of understanding of the organizational change as among the most frequent causes of ERP failure. A lead named at scoping plans communications and training at the project's pace, rather than three weeks before go-live when it is too late.

Which role represents the users in an IT project?

The business analyst represents the project's “customers”. They master the needs, work with process owners and take part in testing until the solution is accepted. They do not replace the key users themselves, who must be freed from their daily tasks to validate processes, but they structure and defend the users' voice within the team.