PMO Maturity: Stages, Assessment Questions and Improvement Steps

PMOs are often judged on paperwork: how many templates they publish, how many reports they produce, how many projects pass through their gates. A better test is whether the organisation delivers more of the right things, more predictably, because the PMO exists. Maturity assessment is how you find out. It shows where your PMO stands, where the gaps are and what to improve next.

This guide explains why maturity matters, the typical stages of PMO maturity, the dimensions worth assessing, a practical set of assessment questions, how to run an assessment, and how to improve without adding bureaucracy.

What "PMO maturity" means

Maturity describes how consistently, effectively and deliberately an organisation manages its projects, programmes and portfolios, and how well the PMO supports that. A mature PMO is not one with the most process. It is one whose practices fit the organisation's needs, are actually used, and improve over time.

Our glossary entry on PMO maturity gives a short definition. This guide goes into how to assess and improve it.

Why assess maturity

• To find gaps between what the PMO does and what the organisation needs.
• To build a case for investment in the PMO, or for simplification.
• To prioritise improvements rather than chasing every best practice at once.
• To measure progress over time and show the PMO's value.
• To reset the mandate when leadership, strategy or the portfolio changes.

An assessment is especially useful when a new PMO lead takes over, when leaders question the PMO's value, or after a major delivery failure.

Five typical stages

Different models use different names. A generic five-stage view looks like this:

Do not treat the top stage as the target for every organisation. A small organisation with a handful of simple projects may be well served at stage 2 or 3. The right target depends on the size, risk and strategic importance of the portfolio.

Recognised maturity models

Several published models offer more detailed frameworks:

• PMI's organisational project management (OPM) standard describes how organisations align project, programme and portfolio management with strategy.
• P3M3®, part of the PeopleCert portfolio, assesses portfolio, programme and project management maturity across several perspectives.
• Capability maturity approaches derived from software and process improvement apply similar staged thinking to project delivery.

You do not need a formal model to start, but using one makes assessments more consistent and easier to compare over time.

What to assess

Look across several dimensions rather than producing a single score. An organisation can be mature in reporting and immature in benefits realisation at the same time.

1. Governance: Are decision rights, stage gates and escalation paths clear and actually used?
2. Delivery methods: Are approaches fit for the work, including agile and hybrid where appropriate?
3. Portfolio management: Is there a single view of demand, capacity and priorities? Are projects stopped when they should be?
4. Resource management: Can the organisation see who is available and who is overloaded?
5. Reporting and metrics: Do reports lead to decisions, or are they filed?
6. Benefits realisation: Are benefits defined, owned and checked after delivery?
7. Risk management: Are risks escalated and aggregated across the portfolio?
8. People and capability: Do project managers receive training, coaching and career paths?
9. Tools and data: Is information reliable, current and easy to update?
10. Culture and sponsorship: Do leaders support the PMO, and do teams see it as helpful?

A simple scoring grid

Score each dimension from 1 to 5 using the stages above, and record the evidence for each score.

The gap between current and target, weighted by business pain, shows where to focus.

Assessment questions

Use questions that reveal practice, not intention:

• If I asked three project managers what the PMO does, would the answers match?
• When a project goes red, what happens next? Is it clear who decides?
• How many projects started last year with a business case? How many were stopped?
• Which reports do executives actually read, and what decisions did they lead to?
• Does the PMO know its capacity limits before new work is accepted?
• Do we measure benefits after projects close? Who owns them?
• How long does it take to get an accurate list of all active projects?
• What do teams say the PMO adds, and what do they say it costs them?
• What would happen if the PMO disappeared tomorrow?

Collect evidence, not only opinion: documents, meeting minutes, dashboards, decision logs and examples of real decisions.

How to run an assessment

1. Agree the purpose with the sponsor. Is the aim to justify investment, reset the mandate or plan improvements? The purpose shapes the scope.
2. Choose the dimensions and the model. Use a published model or the generic grid above.
3. Gather evidence. Review documents and data, observe governance meetings and look at a sample of projects.
4. Interview a cross-section. Include executives, sponsors, project managers, team members and finance.
5. Score and validate. Score each dimension, then test the scores with the people you interviewed. Surprises at this stage are useful.
6. Prioritise. Choose two or three improvements that address the biggest business pain.
7. Report briefly. A short report with clear priorities is more useful than a long one.
8. Repeat. Reassess every 12 to 18 months, or when circumstances change.

Common assessment mistakes

• Self-assessment only. PMOs tend to score themselves higher than their customers do.
• Scoring documents, not practice. A process that exists on paper but is not used is not mature.
• A single number. An overall score hides the dimensions that matter.
• Aiming for level 5 everywhere. Target maturity should follow need.

Improving without adding bureaucracy

1. Pick two or three improvements. Trying to move on every dimension at once causes fatigue.
2. Remove before adding. If a template or report is never used, retire it.
3. Pilot with willing teams. Prove value before mandating.
4. Tie changes to a pain point. Sponsors support what solves a problem they feel.
5. Make data easier. Reporting that is a by-product of work is more accurate than separate returns.
6. Measure and share. Show what changed and what it saved or enabled.
7. Build skills. Process without capability fails. Consider structured learning for PMO staff; see our PMO certification guide.

Example improvement roadmap

Each step builds on the last, and none adds a heavy process.

Who should run the assessment?

For a first assessment, a PMO-led review with independent challenge from a sponsor or outside reviewer is usually enough. For a major reset, or when leaders doubt the PMO's value, independence matters more.

Signs your PMO is moving backwards

Maturity can fall as well as rise. Watch for:

• Reports that nobody reads, or that are produced out of habit.
• Projects bypassing the intake gate because the gate is too slow.
• Shadow registers kept by departments because the official one is unreliable.
• Rising numbers of exceptions to standards, with no review of whether the standards still fit.
• Loss of sponsorship after a leadership change, with nobody restating the PMO's mandate.
• Staff turnover in the PMO that takes knowledge with it.

Each of these is a reason to reassess before a crisis forces the question. Catching them early is far cheaper than rebuilding trust in the PMO later.

Maturity and the type of PMO

Maturity targets differ by PMO model:

• Supportive PMOs focus on capability, templates and coaching. Their maturity shows in how widely good practice is adopted voluntarily.
• Controlling PMOs focus on standards and governance. Their maturity shows in consistent, lightweight compliance.
• Directive PMOs manage projects directly. Their maturity shows in delivery performance.
• Enterprise PMOs focus on the portfolio. Their maturity shows in better investment decisions and benefits realised.

Linking maturity to value

The point of maturity is value, not a higher score. A useful way to keep that in view is to link each dimension to a business outcome:

When you report maturity, report these outcomes alongside the scores.

A short example

A government agency's PMO scored itself at stage 4: it had a full life cycle, templates for every stage and a monthly portfolio report. An independent review told a different story. Project managers completed the templates after decisions had been made. The portfolio report was produced on time but rarely discussed. No project had been stopped in two years.

On evidence, the agency was at stage 2 in governance and portfolio management, even though its documentation looked like stage 4. The improvement plan cut the templates by half, moved the portfolio review into the executive meeting, and added one question to every review: what should we stop? Within a year, three low-value projects had been closed and their budgets moved to priority work. The PMO's documentation got smaller, and its maturity went up.

Further reading

Our glossary defines PMO maturity and related terms such as benefits realisation. For the distinction between projects, programmes and portfolios, which underlies PMO design, read project, programme and portfolio explained. If you are building PMO skills, our PMI-PMOCP guide covers PMI's PMO certification.

Get free certification pathway advice →

Next step

If you are building or reviewing a PMO and want to develop your team's skills, tell us your context and we will suggest relevant learning paths.

Request a corporate training proposal →