Home / Agile PM and Project Management / What Is a PMO? Types, Roles and When You Need One

What Is a PMO? Types, Roles and When You Need One

Project management office team reviewing a portfolio dashboard and delivery roadmap

A PMO (project management office) is the function that standardises, supports or directs how an organisation runs its projects. It can be a small team that shares templates, a group that audits delivery against standards, or a directive office that manages projects itself. The right model depends on how much control your organisation needs and how mature its project delivery already is.

What does a PMO actually do?

Most people meet the PMO as a reporting requirement. In practice a healthy PMO does four things: it sets common methods and templates, it tracks portfolio health, it supports project managers with coaching and resources, and it connects delivery to strategy so the right projects get funded.

That last point is what separates a strategic PMO from an administrative one. An office that only collects status reports adds cost. An office that helps leadership decide which projects to start, pause or stop adds value.

The three PMO types

  • Supportive: provides templates, best practices, training and lessons learned. Control is low, and project teams choose whether to use what is offered.
  • Controlling: requires compliance with specific methods, forms or governance. It audits and reports, but does not run the projects.
  • Directive: takes direct control and manages the projects. Project managers sit inside the PMO and report to it.

Most organisations start supportive and move towards controlling as projects become larger or more regulated. Jumping straight to directive without trust from the business usually creates resistance.

Core PMO roles

  • PMO director or head: owns the PMO strategy and reports to senior leadership.
  • Portfolio or governance analyst: maintains the project pipeline, priorities and dependencies.
  • Project coach or methodology lead: maintains standards and supports project managers.
  • Reporting and data specialist: turns project data into dashboards that support decisions. This is where the difference between reporting numbers and solving problems matters; see our piece on people analytics for the same principle applied to HR data.

PMO roles also overlap with product and analysis roles. If you are mapping responsibilities, read where the business analyst, product owner and project manager roles diverge.

Signs your organisation needs a PMO

  • Different teams report project status in different formats, so leadership cannot compare them.
  • Projects start without a clear link to strategy, and few are ever stopped.
  • The same delivery mistakes repeat because lessons learned are never collected.
  • Resources are double-booked across projects with no one owning the conflict.
  • Governance or regulatory requirements demand consistent evidence of control.

Why many PMOs fail

PMOs usually fail for one of three reasons: they are set up as a policing function without delivering any help, they measure activity (reports produced) instead of outcomes (projects delivered to value), or they lack executive sponsorship. A PMO that cannot show how it improved delivery will be the first thing cut when budgets tighten.

For hands-on training in this area, see the Advanced Project Management Office PMO Establishment course, and for leaders who already run a PMO, Mastering PMO Leadership & Governance for Strategic Impact.

PMO FAQ

Is a PMO only for large organisations?

No. Smaller organisations often run a lightweight supportive PMO of one or two people. The model should match the number and complexity of projects, not the company headcount.

Does a PMO work with Agile teams?

Yes. An Agile-ready PMO shifts from enforcing fixed plans to enabling outcome-based roadmaps, shared tooling and lightweight governance, and it supports teams instead of policing them.

What is the difference between a PMO and a project manager?

A project manager delivers a specific project. A PMO works across many projects, setting standards, tracking the portfolio and supporting the people who deliver.

How do you measure whether a PMO is working?

Look at outcomes: share of projects delivered to scope, schedule and benefit, stakeholder satisfaction, resource utilisation and how fast poor projects are stopped.

Leave a Reply

Agile Leaders Training Center

Turn what you read into skills your team can use

Browse our professional training courses in leadership, HR, project management, quality, risk and more.

Explore our courses

Questions? sales@agile4training.com