Portfolio Management
How the organization governs, prioritizes, and optimizes its portfolio of programs and projects — the decisions made before any delivery work starts.
Most transformation post-mortems name the programme. The honest answer is usually the delivery capability it was handed to. This scores that capability across portfolio governance, programme execution, and implementation — 45 questions, against five maturity levels.
A 3.03 average reads as healthy until you notice portfolio governance sitting at 2.4. That is the number that sets the ceiling for the other two.
Each domain carries 15 questions and is scored on its own. The overall number is an average, and averages hide exactly the thing you need to see — which is why the domain scores are the output that matters.
How the organization governs, prioritizes, and optimizes its portfolio of programs and projects — the decisions made before any delivery work starts.
How individual programs and projects are actually delivered across the core knowledge areas — scope, schedule, cost, quality, risk, and the people around them.
How the technical and organizational sides of delivery actually land — process, change management, data, testing, cutover, and whether any of it sticks after go-live.
Answer as things actually are rather than as they are meant to be — the report is only useful if the input is. Set aside the time: progress is held in the browser and is not saved to an account.
How the organization governs, prioritizes, and optimizes its portfolio of programs and projects — the decisions made before any delivery work starts.
0 of 15 answered — answer all to continue.
Every question scores 1 to 5. Each domain averages its 15 answers, and the overall score averages all 45. That average rounds to one of five levels. Most enterprises land at 2 or 3 — which is a workable place to start from, and a bad place to pretend you are not.