P3O Overview
What the exam tests
This domain checks whether you can explain what a P3O is, why it exists and how it differs from a single project office. A P3O is a decision-enabling and support model for portfolios, programmes and projects. It brings together the offices, functions and services that help leaders choose, govern, assure and deliver change. It is not a project, and it is not simply an administrative team.
Core rules
- A P3O exists to add value: better prioritisation, visible dependencies, reliable reporting, assurance and efficient use of scarce resources.
- It can be permanent (portfolio office, CoE) or temporary (programme/project office), and it may combine several office types.
- Services must be defined and agreed; an office that only produces templates is not demonstrating P3O value.
- Governance and delivery support are different: P3O supports decision-makers without taking accountability for portfolios, programmes or projects.
- Design starts from need and context, not from an org chart.
Worked example
A firm runs 40 change projects, has no single priority list and duplicate reporting. A project office alone would improve individual project reporting but not the portfolio problem. The reasoning points to a portfolio office for prioritisation and dependency management, plus a Centre of Excellence for standards and reporting rules.
Traps
Calling every PMO a P3O; assuming one office must provide all services; treating P3O work as secretarial support; ignoring the cost of duplicated offices.