3.1 Functional, Matrix and Projectised Structures

APM Project Management Qualification PMQ

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current Exam Facts 1.2 Exam Format & Question Types 1.3 How to Study for APM PMQ

2 Life Cycles

2.1 Linear Life Cycles and Why Work Is Phased 2.2 Iterative and Hybrid Life Cycles 2.3 Project Life Cycles and Extended Life Cycles 2.4 Choosing a Life Cycle: Context, Culture, Strengths and Limitations

3 Governance Arrangements

3.1 Functional, Matrix and Projectised Structures 3.2 Governance Frameworks, Policies and Delegated Responsibility 3.3 Life-Cycle Impact on Governance and Limits of Financial Authority 3.4 Project Roles and Responsibilities 3.5 Project Manager and Project Sponsor Through the Life Cycle 3.6 Linking Projects to Organisational Objectives

4 Sustainability

4.1 Sustainability Responsibilities, Principles and Impact 4.2 Monitoring and Reporting Sustainability Measures

5 Business Case

5.1 Business Case Fundamentals and Analysis Tools 5.2 The Business Case as Baseline and Reviewing Change

6 Procurement

6.1 Procurement Strategy: Purpose and Contents 6.2 Supplier Selection and Negotiation 6.3 Features of Different Contractual Relationships 6.4 Supplier Reimbursement Methods

7 Reviews & Assurance

7.1 Reviews, Decision Gates, Benefits Reviews and Audits 7.2 What Gets Reported and Informing Decisions 7.3 Why Activities Are Re-Planned After a Review 7.4 Project Assurance

8 Transition & Benefits Management

8.1 Transition Requirements and Business-as-Usual Readiness 8.2 Knowledge Transfer and Agreeing the Transition Plan 8.3 Benefits Management: Identification to Realisation 8.4 Aligning and Communicating Benefits

9 Stakeholder Engagement & Communication

9.1 Stakeholder Analysis, Influence and Engagement 9.2 The Communication Management Plan and Its Benefits 9.3 Managing Stakeholder Expectations 9.4 Communication Methods and Tailoring the Message 9.5 Factors That Help and Hinder Communication

10 Conflict Resolution

10.1 Sources and Impacts of Conflict 10.2 Addressing Conflict and the Thomas-Kilmann Model

11 Leadership

11.1 Leadership, Motivation and Team Performance 11.2 Changing Leadership Styles for the Situation 11.3 Coaching, Mentoring and Emotional Intelligence

12 Team Management

12.1 Team Development Stages and Models 12.2 Characteristics and Benefits of Effective Teams 12.3 Leading Virtual and Hybrid Teams

13 Diversity & Inclusion

13.1 Diversity Characteristics and the Equality Act 13.2 Incorporating Diversity and Diverse Thinking 13.3 Conscious and Unconscious Bias and Fair Treatment

14 Ethics, Compliance & Professionalism

14.1 Continuing Professional Development and Competence 14.2 Sources of Specialist Advice and Standards 14.3 The Legal and Regulatory Landscape

15 Requirements & Solutions

15.1 Establishing Scope Through Requirements Management 15.2 Managing Scope Through Configuration Management 15.3 Solutions Development and Prioritisation

16 Quality Management

16.1 Quality Planning, Indicators and the Business Case 16.2 Quality Control and Success Criteria

17 Integrated Planning

17.1 The Integrated Project Management Plan: Format and Contents 17.2 Why an Integrated Plan Matters

18 Schedule Management

18.1 Defining Scope and Breakdown Structures 18.2 Dependencies and What Drives the Schedule 18.3 Re-Estimating and Schedule Optimisation

19 Resource Management

19.1 Determining Resource Requirements and Availability 19.2 Organisational Breakdown Structure and RACI 19.3 Categorising and Allocating Resources 19.4 Resource Smoothing and Resource Levelling

20 Budgeting & Cost Control

20.1 Creating a Budget and Cost Types 20.2 Earned Value and Cost Forecasting 20.3 Monitoring and Reporting Financial Performance 20.4 Closing Down Project Finances

21 Risk & Issue Management

21.1 Benefits of Risk and Issue Management and Contingency Planning 21.2 The Risk and Issue Management Processes 21.3 Proactive and Reactive Risk Responses 21.4 Governance in Risk and Issue Management

22 Change Control

22.1 The Change Control Process and Its Stages 22.2 What a Change Request Must Capture 22.3 Assessing Options and the Impact of a Change 22.4 Recommending Decisions and Updating Plans

Free exam prep APM Project Management Qualification (PMQ) Practice Questions 135 questions Study Guide 74 topics

3.1 Functional, Matrix and Projectised Structures

Key Takeaways Explain This Topic AI

Governance is the framework of authority and accountability for delivering a project so that it aligns with organisational practice and decision rights.

Permanent structures own people, budgets, and corporate rules; temporary project structures exist only while the project needs coordinated cross-unit effort.

In a functional structure the project manager has low formal authority and negotiates for time against business-as-usual priorities.

In a matrix structure staff report to both a functional manager and a project, so dual reporting makes clear roles, RACI, and escalation essential.

In a projectised structure the project manager usually controls team and budget, but staff reassignment and corporate standards need deliberate attention. Last updated: August 2026

What Governance Means on the APM PMQ The APM PMQ syllabus defines governance arrangements as the framework of authority and accountability for delivering a project in a way that aligns with organisational practice . Governance is not the same as day-to-day project management. The project manager plans, directs, and controls delivery work; governance decides who is allowed to decide what , how investment is released, which standards must be followed, and when the organisation should continue, change, or stop the project. On long-response questions, weak answers list controls without purpose. Strong answers link structure → decision rights → control of benefits, risk, and spend. Always ask: who is accountable, who has authority, and how does this project fit the host organisation’s way of working? Permanent vs Temporary Organisation Structures Most organisations are permanent : they exist to run ongoing operations (business-as-usual). Projects are usually temporary : they have a start, an end, and unique outputs. Governance must bridge both worlds.

Dimension Permanent organisation Temporary project structure Purpose Sustain products, services, and operations Deliver a defined change or unique output Duration Ongoing Finite (closed when objectives are met or work stops) Authority base Line management, functional heads, corporate policies Sponsor, steering group/board, delegated project roles Resource model Staff sit in departments with stable reporting lines People are assigned (full-time or part-time) for the project’s life Success measure Operational performance, service levels, BAU KPIs Project objectives, benefits case, agreed tolerances The permanent structure owns people, budgets, and corporate rules. The temporary structure exists only while the project needs coordinated effort across those permanent units. When the project closes, temporary roles dissolve and outputs, risks, and benefits ownership transfer into business-as-usual. Exam trap: Treating the project team as a permanent department. On the PMQ, projects remain temporary even when they last years; governance still plans for closure, handover, and dissolution of the temporary structure. Functional, Matrix, and Projectised Structures The syllabus expects knowledge of three classic permanent (or semi-permanent) structural types and their features. In practice many organisations are hybrids, but exam scenarios usually map cleanly to one dominant form.

Structure How work is organised Project manager authority Typical strengths Typical tensions for the PM Functional People and budgets sit in specialist departments (engineering, finance, operations) Low — PM often coordinates across functions with limited formal power Deep specialist expertise; clear career paths; efficient for routine BAU Resource priority fights with BAU; slow cross-functional decisions; PM may lack budget/people authority Matrix Staff report to functional managers and contribute to projects Medium — shared authority with functional heads Flexible use of scarce skills; visibility of project vs BAU demand Dual reporting, role ambiguity, contested priorities; needs strong RACI and escalation paths Project (projectised) People and resources are organised primarily around projects High — PM usually controls team and budget for the project Clear focus, fast decisions, strong team identity Specialist silos may weaken after project ends; under-use of corporate standards if not enforced Functional structures In a functional organisation, departments own their people. A project may be run within one function (for example, an IT upgrade led by the IT director) or coordinated across several functions by a project manager who has little formal power. Governance often flows through existing line management. Stage decisions may sit with a departmental head rather than a dedicated project board unless the investment is large enough to justify one. Advantage for the organisation: specialist quality and efficient utilisation of experts when project demand is occasional. Tension for the PM: negotiating time from busy line managers, resolving conflicts when BAU work trumps project tasks, and escalating when no single senior owner has enterprise-level accountability. Matrix structures Matrix structures are common for organisations that run many projects alongside operations. People keep a functional home (for career, competence, and often appraisal) while allocating a percentage of time to projects. Matrix forms range from weak (functional managers dominate) through balanced to strong (project managers hold more power over priorities and performance input). Advantage: scarce specialists can serve multiple initiatives without permanent reorganisation. Tension: dual reporting creates ambiguity. Without clear governance, team members receive conflicting instructions from a functional head and a project manager. The PMQ expects you to recognise that governance — role definitions, RACI, escalation routes, and priority rules set by senior management — is what makes a matrix workable. Projectised structures In a projectised (project-based) organisation, the primary unit of work is the project. Teams form around initiatives; the project manager typically has direct authority over people and budget for that work. Consulting firms, construction delivery units, and product delivery organisations often lean this way. Advantage: speed, focus, and clear day-to-day authority for the PM. Tension: when the project ends, staff need reassignment; corporate governance must still ensure standards, assurance, and strategic alignment so individual projects do not optimise locally while harming the portfolio. Scenario: same project, three structures A hospital is implementing a new electronic patient-record system. Functional: IT leads technical work; clinical departments second staff ad hoc. The PM spends most of their time securing clinician time and may lack power to stop clinical BAU from delaying testing. Matrix: clinicians are allocated 40% to the programme; functional heads and the programme board jointly set priorities. Conflicts go to a steering group that owns both clinical safety and investment. Projectised: a dedicated delivery team is seconded full-time under a programme director with budget control. Decisions are faster, but the organisation must plan how clinical specialists return to wards after go-live. In each case the technical work may be similar; the governance challenge (authority, escalation, resource priority) differs.

Test Your Knowledge

In a matrix organisation, why is clear project governance especially important for the project manager?

Because matrix structures remove the need for a project sponsor

Because the project manager always owns all functional staff permanently

Because team members often have dual reporting lines and competing priorities that need defined authority and escalation

Because financial authority limits never apply in matrix structures Check Answer Need a hint? AI

Test Your Knowledge

A specialist engineering firm runs occasional internal improvement projects. Staff sit permanently in discipline departments, budgets are held by department heads, and project managers coordinate across those departments without formal authority over people. Which structure is described, and what is the project manager’s main governance challenge?

Functional — the challenge is securing time from line managers when business-as-usual work competes for the same people

Matrix — the challenge is that the project manager holds full budget authority and must account for it

Temporary — the challenge is that no permanent organisation exists to receive the outputs

Projectised — the challenge is reassigning staff when the project closes Check Answer Need a hint? AI

Sections you finish are checked off in the contents.

Up Next 3.2 Governance Frameworks, Policies and Delegated Responsibility Continue learning

Independent exam preparation notice OpenExamPrep is an independent education provider, not affiliated with or endorsed by the exam sponsors named on this site. Exam and certification names identify what our resources help you study for; they do not imply sponsorship, approval, or review of our materials. Unless a resource expressly identifies authorized public material, our practice questions are independently developed simulations, not actual, recalled, or sponsor-provided exam items. We aim to reflect publicly available exam outlines and topic information in our study resources. Coverage, format, and difficulty may differ from the actual exam, and we cannot guarantee that every detail is accurate or current. Confirm exam requirements, fees, and policies with the official exam sponsor.