2.3 Principle 3: Define Roles, Responsibilities and Relationships

2.3 Principle 3: Define Roles, Responsibilities and Relationships

Projects involve cross-functional teams comprising people from different departments, functional units, or external vendor organizations. In routine operations, individuals report to their functional line managers. However, a project creates a temporary organizational structure that cuts across permanent functional boundaries. Without explicit clarity on who is responsible for what, project decisions stall, accountability vanishes, and conflict arises.

PRINCE2 Principle 3: Defined Roles and Responsibilities mandates that a project must establish an explicit management structure engaging the three primary stakeholder interests: Business, User, and Supplier.

PRINCE2 Principle Rule: A PRINCE2 project has defined and agreed roles and responsibilities within an organizational structure that engages the business, user, and supplier stakeholder interests.

---

The Three Primary Stakeholder Interests (BUS)

Every PRINCE2 project must balance three distinct stakeholder perspectives on the Project Board:

+-----------------------------------------------------------------------------------+
|                         PROJECT BOARD STAKEHOLDER INTERESTS                       |
+-----------------------------------------------------------------------------------+
|  1. BUSINESS (Executive)      | Ensures project delivers value for money & ROI     |
|  2. USER (Senior User)        | Specifies requirements & realizes product benefits |
|  3. SUPPLIER (Senior Supplier)| Provides technical capability, resources & quality  |
+-----------------------------------------------------------------------------------+

1. Business Interest (Represented by the Executive)

• Ensures the project aligns with corporate strategy and delivers value for money.
• Holds ultimate accountability for the project and owns the Business Case.
• Secures project funding.

2. User Interest (Represented by the Senior User)

• Represents those who will use the project's final products to realize business benefits.
• Defines operational user requirements and quality acceptance criteria.
• Monitors whether delivered products satisfy user needs in operational practice.

3. Supplier Interest (Represented by the Senior Supplier)

• Represents those who design, build, procure, or implement the project's products (internal specialists or external contractors).
• Provides technical expertise, engineering resources, and craftsmanship.
• Accountable for the quality of delivered technical materials and specialist outputs.

---

The Four Levels of Management

PRINCE2 structures project governance into four distinct management levels:

---

Specific Role Breakdown in PRINCE2

In addition to the main management tiers, PRINCE2 defines specific support and control roles:

Project Assurance

• Purpose: Provides independent monitoring of project performance on behalf of the Project Board.
• Three Strands: Business Assurance (Executive interest), User Assurance (Senior User interest), and Supplier Assurance (Senior Supplier interest).
• Critical Governance Rule: Project Assurance must be completely independent of the Project Manager. The Project Board cannot delegate assurance responsibilities to the Project Manager, as that would create a conflict of interest (self-auditing).

Change Authority

• Purpose: Delegated by the Project Board to review and approve requests for change or scope modifications within agreed change budget tolerances.
• Flexibility: The Project Board can act as the Change Authority itself or delegate this role to the Project Manager or a dedicated Change Committee for efficiency.

Project Support

• Purpose: Provides administrative, filing, scheduling, and secretarial support to the Project Manager.
• Flexibility: Can be provided by a dedicated Project Management Office (PMO) or handled directly by the Project Manager on smaller projects.

---

Combining and Splitting Roles: Exam Rules

PRINCE2 explicitly distinguishes between roles (defined responsibilities) and people (individuals assigned to roles). Depending on project scale, one person may fulfill multiple roles, or one role may be shared by multiple people.

However, strict rules govern role assignment for Foundation exams:

+-----------------------------------------------------------------------------------+
|                       ROLE COMBINATION RULES (EXAM CRITICAL)                       |
+-----------------------------------------------------------------------------------+
|  ALLOWED COMBINATIONS                  |  FORBIDDEN COMBINATIONS                  |
|  * Executive + Senior User (Internal)  |  * Executive + Project Manager           |
|  * Project Manager + Team Manager      |  * Project Manager + Project Assurance   |
+-----------------------------------------------------------------------------------+

1. Executive and Project Manager CANNOT be combined. The Executive provides direction and oversight; combining this with day-to-day management destroys accountability.
2. Project Manager and Project Assurance CANNOT be combined. A Project Manager cannot independently audit their own management work.
3. Executive and Senior User CAN be combined if the project is internal and the Executive directly manages the user department.
4. Project Manager and Project Support CAN be combined on small, low-complexity projects where separate admin staff is unnecessary.

---

People and Leadership Dynamics in PRINCE2 7

The People element in PRINCE2 7 emphasizes that assigning role names on an organizational chart is insufficient. Effective leadership requires:

• Clear communication channels between levels.
• Active stakeholder management across internal and external boundaries.
• Establishing clear decision-making authority so team members do not experience conflicting orders from line managers and Project Managers.

---

Summary Matrix: Management Level vs. Role Accountability