A PMO’s role is what it answers for to the person who gave it its mandate; its responsibilities are the recurring activities through which it fulfils that role. Both are set according to the level at which the office is placed: a project, a programme or a portfolio.
At project level, the PMO maintains the management instruments on behalf of the person leading the project. At programme level, it maintains what links the projects: overall plan, dependencies, common risks, benefit tracking. At portfolio level, it prepares senior management’s choices between projects. At all three levels, it prepares decisions that others take, unless its mandate says otherwise. The notion itself and its variants of authority appear in our entry on the definition of the PMO, and the boundary with the project manager in our article on the difference between a PMO and a project manager.
PMO role and responsibilities by level
| Project PMO | Programme PMO | Portfolio PMO | |
|---|---|---|---|
| Principal | The project manager or project director | The programme director | The management that arbitrates: CIO, executive management, portfolio committee |
| Role | Maintaining the project’s management instruments | Maintaining what links the programme’s projects | Preparing the choices between projects and programmes |
| Objects maintained | Schedule, budget, risk register, decision logs | Overall plan, dependency register, common risks, benefit tracking | Single list of projects, priority criteria, view of capacity, arbitration calendar |
| Recurring responsibilities | Updating, checking consistency, preparing the steering committee, following up actions | Consolidating plans, running synchronisation between projects, preparing the programme committee | Qualifying requests, consolidating project status, preparing arbitrations, maintaining the common framework |
| Decisions prepared | Those of the project manager and the steering committee | Arbitrations between projects, moving from one release stage to the next | Admitting, postponing and stopping projects |
| End of mandate | At project closure | At programme closure | None: the function is permanent |
This table is a reading grid. Each PMO’s written mandate is authoritative, and an organisation may split certain responsibilities differently. The portfolio PMO here covers what our glossary calls the enterprise PMO.
The level first designates a principal
The first line of the table governs the others. The same acronym covers three offices, to the point that the letter P reads project, programme or portfolio depending on the scope. What separates them in practice is the person to whom the PMO hands over its work.
The project PMO extends the function of the person leading the project: it maintains for them, and under their authority, the schedule, the budget and committee preparation. The programme PMO works for the programme director, who answers for an overall result. The portfolio PMO works for a management that chooses between competing projects.
The job title tells you less than the answer to one question: to whom does this PMO hand what it produces, and for what decision? A PMO that names two recipients at two levels performs two roles, to be written down separately.
From project to programme, the work moves between the projects
At project level, the PMO’s material is inside the project. It updates the schedule with the teams, reconciles actual spending with the budget, maintains the risk register and checks that these instruments say the same thing: the date in the schedule is the one that appears in the report submitted to the committee.
At programme level, this material stays with the projects. The programme PMO does not redo their schedules: it works on what no project manager holds alone. Its responsibilities concern the milestones at which one project awaits another’s delivery, the risks that several projects share and the benefits the programme has promised.
This shift has consequences. The PMO depends on information produced by project managers who do not report to it. Its first responsibility is therefore to agree common definitions with them, starting with what a milestone reached means. The committee it prepares also changes its subject: the progress of each project is read before the meeting, and the agenda concerns the arbitrations to be made between projects. The decision remains with the programme director, whose function is described on our page on programme management.
At portfolio level, the PMO prepares choices
The projects of a programme contribute to the same result. Those of a portfolio compete for the same budget and the same teams, whether or not they are linked to one another. The role therefore changes in nature: having coordinated, the PMO now prepares cases for decision.
Its responsibilities follow the arbitration cycle. It maintains the list of projects in progress and projects requested. It obtains for each request a description comparable to the others. It compares the whole with the available capacity, then prepares the committee’s files and follows up the application of its decisions. The corresponding discipline is described in our entry on PPM, and its implementation on our page on project portfolio management.
Maintaining the common framework (method, templates, definitions) and supporting project managers, including training them in common practices, also sit at this level, because they require a permanent structure. A project or programme PMO disappears with its object and cannot carry them over time.
The portfolio PMO does not follow each project day to day. It consolidates what projects declare and checks that these declarations are comparable.
When several levels coexist
A large organisation may bring all three together: a PMO on its largest project, another on a programme, a third at portfolio level. Coexistence works on one condition: each piece of information is produced once, at the lowest level, then consolidated upwards without re-entry. The upper level sets the definitions and the calendar, and each level adds its own object.
Some drifts signal a responsibility entrusted to the wrong level:
- a project PMO asked to arbitrate between its project and the others, with neither an overall view nor a mandate to do so;
- a portfolio PMO that maintains each project’s schedule, and no longer has time to prepare choices;
- a programme PMO kept on after the end of the programme, which becomes a de facto portfolio PMO, without a written mandate;
- two levels asking the same project manager for two reports in different formats.
In each case, the remedy goes through the mandate: its content, its reporting line and the function’s resources, covered on our page on setting up a PMO.
The decision that comes before all the others concerns a name, that of the person to whom the PMO will hand over its work. That name sets the level, the level sets the role, and the responsibilities follow from it.