PMO Maturity Assessment: Score Your Team in 20 Minutes

Here's a test you can run before reading any further: name your PMO's weakest of these five, process, tooling, governance, risk, and reporting, without checking a document first. If you can't, that's the assessment result. Most PMOs know they aren't perfect; few can say precisely where the gap is or what it's costing them.

The direct answer: a PMO maturity assessment scores five dimensions, process, tooling, governance, risk, and reporting, from 0 (doesn't exist) to 3 (consistent and measured), for a total out of 15. The total maps to a tier: Ad-Hoc (0-3), Emerging (4-6), Defined (7-9), Optimized (10-12), or Enterprise (13-15). The score matters less than which single dimension is dragging the total down, because that's the one worth fixing this quarter.

The Five Dimensions of a PMO Maturity Assessment

These are the same five dimensions the PMO maturity tiers guide walks through in depth: process (are intake, planning, and closure steps written down and followed), tooling (does the PMO's system of record hold real data or a stale export), governance (do gate reviews and sign-offs actually happen before money moves), risk (is there a live register with named owners, not a spreadsheet nobody opens), and reporting (do status numbers come from the schedule or from what the PM believes). A PMO can be strong on one dimension and weak on another; that's the point of scoring them separately instead of asking one vague "how mature are we" question.

How to Score Each Dimension

Score every dimension on the same 0-3 scale, using the honest answer, not the aspirational one.

Score	What it means	Example (Governance)
0	Doesn't exist	No gate reviews; projects start when someone starts working
1	Ad hoc	Reviews happen sometimes, for some projects, informally
2	Documented but inconsistent	A gate process exists on paper; roughly half of projects actually go through it
3	Consistent and measured	Every project clears defined gates; skip rate is tracked and near zero

Run this against all five dimensions and write down the number, not a description. A PMO that scores itself a 3 on reporting because "we send a weekly email" is scoring the activity, not the outcome; the real question is whether that email's numbers come from the schedule or from a PM's gut feel, which is a 1 at best.

The diagram below shows how the five dimension scores roll up into one total, and how that total lands on the tier ladder.

What Your Total Score Means

Tier	Score	What it looks like
Ad-Hoc	0-3	No PMO practice is written down; each PM runs projects their own way
Emerging	4-6	Some practices exist but depend on who's running the project
Defined	7-9	Standards are written and mostly followed; the common plateau for PMOs under 30 projects
Optimized	10-12	Standards are enforced and measured; gaps get caught before they become incidents
Enterprise	13-15	All five dimensions are integrated: a risk flagged in reporting triggers a governance check automatically

Enterprise isn't the goal for every PMO. A 15-project PMO that reaches Defined and stays there, with clean process and governance, is in better shape than one burning its PMs out chasing Enterprise-tier integration it doesn't have the portfolio size to need. The five-tier structure here follows the same layered logic as the Capability Maturity Model, where each level assumes the ones below it are already solid; the difference is the goal. Match the target tier to your actual scale instead of defaulting to the top one.

What to Do With a Low Score

1. Circle your lowest single dimension, not your average. A PMO with process at 3, tooling at 3, governance at 0, risk at 2, and reporting at 2 has a governance problem, not a maturity problem; averaging to 2.0 hides that.
2. Name the one practice that would move it from its current score to the next one up. Moving governance from 0 to 1 might just mean starting a gate review for new projects, not building the full pipeline in one quarter.
3. Re-score in 90 days, using the same rubric, so the comparison is apples to apples instead of a fresh, more generous read.
4. Don't fix all five at once. A PMO that tries to raise every dimension in the same quarter usually raises none of them past the ad-hoc stage, because the actual bottleneck is almost always leadership attention, not effort.

The portfolio manager vs. PMO director split matters here too: raising the governance dimension is usually a PMO director's call, while raising reporting quality often sits with whoever owns the enterprise project governance function day to day. Knowing which role owns which dimension is half of what actually moves a low score. The rest of the blog's PMO governance coverage works through the practices behind each dimension in more depth, from responsibility matrices to portfolio triage.

Get the full PMO Maturity Assessment Run the complete 15-question version online and get your tier plus the specific gaps behind each dimension score. No signup required. → Take the free PMO Maturity Assessment