Definition of the PMO
The PMO, for Project Management Office, is a permanent or temporary structure responsible for organising the management of projects within a company or a public body. It is also called a project office. Its purpose is to give decision-makers reliable information that is comparable from one project to another, and to ensure that projects are run according to shared practices.
The term covers two realities that everyday language mixes up. It refers first to the entity, that is, the team or department. By extension, it also refers to the role: a person is said to “be a PMO” when they track the planning, risks, budget and committees of a project or programme.
What a PMO is for
The missions of a project office vary between organisations, but they fall into four families.
- Defining the framework. Project management method, document templates, mandatory milestones, reporting rules.
- Consolidating. Gathering the progress, costs, risks and workload of all projects into a coherent overall view.
- Informing decisions. Preparing steering committees and trade-offs: which projects to launch, reinforce, postpone or stop.
- Supporting teams. Supporting project managers, training in shared practices, capturing lessons learned.
A PMO that only fulfils the first two missions becomes a reporting unit. It is the third that justifies its existence.
The different types of PMO
PMOs are usually classified along two axes.
The first is the degree of authority. The supportive PMO advises and provides tools, without any power of constraint. The controlling PMO checks that the shared framework is applied. The directive PMO manages the projects itself and oversees the project managers.
The second is the scope. The project PMO is attached to a single project, generally a large one. The programme PMO coordinates several projects that contribute to the same objective. The enterprise PMO, sometimes called EPMO, covers the whole portfolio and makes the link with strategy.
| Type | Scope | Main role |
|---|---|---|
| Project PMO | One project | Planning, tracking, project governance meetings |
| Programme PMO | Several related projects | Coordination, dependencies, shared benefits |
| Enterprise PMO | The whole portfolio | Prioritisation, trade-offs, strategic alignment |
PMO, PPM and governance: not to be confused
The PMO is a structure. Project portfolio management, or PPM, is a discipline: the set of practices used to choose and prioritise projects according to strategy and capacity. An enterprise PMO is often tasked with running this discipline, but one does not imply the other.
Project governance, finally, refers to the decision-making bodies and rules: who decides, on what, and when. The PMO equips it and keeps it alive, but it is the sponsors and committees that decide.
A concrete example
Consider an IT department running forty projects in parallel. Each project manager tracks their progress in their own file, with their own colours. At the executive committee, nobody can say how many projects are actually late, or whether the teams have the capacity to launch new ones.
Creating a PMO changes three things. A shared project sheet makes situations comparable. A monthly review consolidates milestones, risks and workload. A quarterly trade-off committee decides, on this basis, which projects to launch and which to stop. None of these measures is spectacular. Together, they allow management to make informed decisions.
Associated skills and certifications
The PMO role requires rigour in planning, a good reading of risks and costs, and above all an ability to obtain honest information from teams. Several frameworks structure these skills, notably those of the Project Management Institute described in our entry on PMI certifications and the method presented in the PRINCE2 entry.
To go further on implementation, see our page devoted to setting up and strengthening a PMO.