PRINCE2 is a structured project management method that separates decision-making, delivery and assurance into clear roles. Understanding PRINCE2 team roles helps prevent overlap, speeds decision-making and keeps everyone accountable. This article outlines the main roles, their responsibilities and practical tips for assigning them on real projects.
The Project Board
The Project Board provides overall direction and authorisation. It comprises three primary members:
• Executive - represents the business and is ultimately accountable for the project delivering the expected benefits.
• Senior User - represents those who will use the project’s products and ensures requirements are met.
• Senior Supplier - represents the interests of those providing the resources and technical expertise.
Collectively the board approves major plans and tolerances, makes funding decisions and resolves issues escalated by the Project Manager.
Project Manager
The Project Manager runs day-to-day project delivery. Typical responsibilities include:
• planning and controlling delivery within agreed tolerances
• managing risks, issues and changes
• reporting progress to the Project Board
• coordinating teams and suppliers
The Project Manager translates the board’s direction into manageable stages and ensures that work is organised to meet quality, cost and time objectives.
Team Manager
Team Managers take responsibility for producing one or more project deliverables. Their duties cover:
• detailed task planning and allocation within the team
• monitoring work progress and quality checks
• reporting status and exceptions to the Project Manager
Not every PRINCE2 project needs a separate Team Manager role; on smaller projects the Project Manager may also act as Team Manager.
Project Assurance
Project Assurance provides independent checking on behalf of the Project Board. It covers three perspectives:
• business assurance (benefits and value)
• user assurance (requirements and acceptance)
• supplier assurance (technical quality and resource adequacy)
Assurance is deliberately independent of delivery so that the board can trust the information on which it makes decisions.
Project Support
Project Support supplies administrative services, tools and information. Tasks commonly include:
• maintaining the issue and risk logs
• arranging meetings and producing minutes
• storing and controlling project documents
Effective support frees the Project Manager to focus on control and leadership.
Change Authority
The Change Authority is often delegated by the Project Board to approve requests for change within a defined scope and cost threshold. This speeds up routine decisions while the Project Board retains control over larger impacts.
Specialists, Suppliers and Stakeholders
• Specialists supply the technical skills or subject matter expertise required to create products.
• Suppliers provide goods or services contracted into the project.
• Stakeholders include any individuals or groups affected by the project; identifying them early helps manage expectations and acceptance.
PRINCE2 recognises that some roles may be combined or adapted depending on project size and complexity.
Practical advice for assigning roles
• Match authority with responsibility: if someone is accountable for an outcome, give them the authority to influence the necessary resources and decisions.
• Keep roles clear on paper: a short role description included in the PID or project brief prevents misunderstandings later.
• Use the Project Board sparingly for operational decisions: reserve it for strategic choices and allow delegated roles to handle routine approvals.
• Ensure independence for assurance: whoever fulfils Project Assurance should not be the same person delivering the work they are checking.
• Scale roles to the project: combine or separate roles to reflect available resource and the risk profile.
Common pitfalls to avoid
• Blurring accountability between Project Manager and Project Board, which leads to slow decisions.
• Underestimating the need for Project Support on documentation-heavy projects.
• Making the Senior Supplier or Senior User a figurehead rather than an active participant, which weakens governance.
Key outcomes from correct role assignment are faster decisions, clearer escalation paths and more reliable reporting.
Final points
PRINCE2 team roles are designed to create separation between governance, management and delivery. Applying those roles thoughtfully and documenting the arrangements will help a project stay on track and enable prompt responses to change.
For details of course content and dates, Browse Knowledge Train training.
Top comments (0)