TL;DR
An enterprise PMO (ePMO) decides which initiatives the organisation funds, keeps them tied to strategy, and checks that they deliver the benefits promised. A PMO runs projects well; an ePMO makes sure they are the right projects. In Australia the case is stronger than ever: fewer than half of digital initiatives hit their business targets, APRA's CPS 230 asks regulated entities to manage change risk across critical operations, and AI pilots are multiplying. The hard part is rarely the framework. It's getting one honest view of the portfolio when the data lives in Jira, Microsoft tools, Salesforce and finance systems that don't talk to each other.
Most organisations already have project managers, status reports and a steering committee. What they often lack is a single place where someone can answer three questions with confidence: what are we spending on change, is it the right work, and is it paying off?
That is the job of an enterprise project management office. This guide covers what an ePMO is, how it differs from a traditional PMO, why it matters for Australian organisations in 2026, and how to set one up without adding bureaucracy.
What is an ePMO?
An enterprise project management office is a function that governs the organisation's whole portfolio of change, across every division, rather than the projects of one team. It sets how initiatives are proposed, prioritised and funded, tracks delivery and risk across the portfolio, and measures whether completed work delivered the benefits in its business case.
The difference from a PMO is scope and purpose:
| PMO | Enterprise PMO | |
|---|---|---|
| Scope | Projects in one function, usually IT | All change across the organisation |
| Main question | Are we delivering projects well? | Are we doing the right work, and is it paying off? |
| Reports to | A function head, such as the CIO | The executive team, often the COO, CFO or CEO |
| Measures | Time, budget, scope, milestones | Strategic fit, capacity, risk, benefits realised |
| Typical outputs | Methods, templates, status reports | Investment decisions, portfolio roadmap, benefits tracking |
An ePMO doesn't replace project or program management. It sits above it, and often sets the minimum standards that project teams follow.
Why the case is stronger in Australia now
- Too much change misses its targets. Gartner's survey for its 2025 CIO Agenda found that only 48% of digital initiatives meet or exceed their business outcome targets. Better project delivery alone won't fix that. Choosing the right initiatives and tracking their outcomes will.
- CPS 230 is in force. APRA's CPS 230 Operational Risk Management standard has applied since 1 July 2025. Banks, insurers and superannuation trustees must identify critical operations, set board-approved tolerance levels for disruption, keep a register of material service providers and manage change risk as part of operational risk. Programs that change critical operations or providers need that risk assessed and tracked across the portfolio, not project by project.
- AI pilots are multiplying. Many organisations now have AI experiments running in several divisions at once, often on overlapping platforms and data. Without a portfolio view, duplication and unmanaged risk follow. The Privacy Act's automated decision rules, which start on 10 December 2026, add a compliance angle.
- Microsoft Project Online has retired. Microsoft retired Project Online on 30 September 2026, with no read-only period. Many PMOs ran their portfolio reporting on it, so the choice of replacement is a chance to rethink how portfolio data is gathered.
- Mid-sized organisations are running enterprise-scale change. Cloud migrations, ERP and CRM replacements and platform consolidation now land on organisations with a few hundred staff, where a single failed program is felt across the business.
What an ePMO actually does
A useful ePMO does five things well:
- Runs one front door for new initiatives. Every proposal arrives in the same format, with a problem statement, expected benefits, rough cost and the capacity it needs.
- Prioritises against strategy and capacity. Initiatives are scored against agreed strategic objectives, then checked against the people and budget actually available. Saying no, or not yet, is part of the job.
- Right-sizes governance. A small, low-risk change shouldn't face the same gates as a core system replacement. Tier initiatives by risk and value, and set the reporting and approvals for each tier.
- Gives one view of the portfolio. Status, spend, dependencies and risk across all initiatives, from data that teams already maintain rather than spreadsheets compiled by hand each month.
- Tracks benefits after go-live. The business case promised something. The ePMO checks, months later, whether it happened, and feeds what it learns into the next round of decisions.
Choosing an operating model
There are three common shapes, and most organisations end up with a blend:
- Centralised: one ePMO team owns portfolio governance and may provide project managers. It gives the strongest control, and suits organisations with heavy regulatory obligations or a single large transformation.
- Federated (hub and spoke): a small central team sets standards and runs the portfolio process, while divisional PMOs manage delivery. It suits larger organisations with distinct business units.
- Lean or advisory: a few senior people run prioritisation and benefits tracking, with delivery left to teams. It suits mid-sized organisations and those with mature agile teams.
Start leaner than you think you need. It's easier to add governance where it's missing than to remove it once people have built processes around it.
The systems an ePMO has to join up
This is where most ePMOs struggle. The information they need is spread across systems that were never designed to work together:
- Delivery work lives where teams plan it: Jira for software and, increasingly, business teams; Microsoft Planner for many Microsoft 365 organisations.
- Portfolio and strategy sit in a portfolio tool. In the Atlassian world that means Plans in Jira Premium for cross-team planning, and Atlassian's Strategy Collection, which pairs Focus, a hub for priorities, key results and funding, with Jira Align. In the Microsoft world, Project Online's recommended successors are the new Planner with Project Plan 3 or 5 for portfolios, Project Server Subscription Edition for advanced needs, and Dynamics 365 Project Operations where project finance and resourcing run through Dynamics.
- Documentation and decisions live in Confluence, SharePoint or both.
- Customer and revenue impact sits in the CRM, such as Salesforce or Dynamics 365.
- Actual spend lives in the finance system or ERP.
If these aren't connected, the ePMO ends up as a reporting team re-keying data into slides, and the portfolio view is out of date before the meeting starts. Connecting them, so that delivery status flows up from Jira or Planner, benefits can be checked against CRM and finance data, and decisions are recorded where people work, is what turns an ePMO from overhead into a decision-making tool. It's the work Great Minds does most often in this space.
Why ePMOs fail
- Seen as bureaucracy. Templates and gates without a visible payoff. Fix it by tiering governance and showing teams what they get back, such as faster approvals and fewer ad hoc status requests.
- No executive teeth. If the executive team funds pet projects outside the process, the process stops meaning anything. The ePMO needs a sponsor with authority over investment decisions.
- Reporting instead of deciding. A beautiful dashboard that never changes a funding decision is an expensive habit.
- One method for everything. Agile teams, waterfall programs and vendor-led projects need different controls. Govern outcomes and risk, not the method.
- Benefits forgotten after go-live. Without someone accountable for checking benefits, business cases become a hurdle to clear rather than a commitment.
A 90-day plan to set one up
- Days 1–30, see the portfolio. Build an inventory of every initiative in flight, with owner, cost, stage and the strategic objective it supports. Expect to find duplicates and zombie projects.
- Days 31–60, agree the rules. Set prioritisation criteria with the executive team, define two or three governance tiers, and design the intake form and decision forum.
- Days 61–90, connect and run. Connect the delivery tools to a single portfolio view, run the first prioritisation round, stop or pause what doesn't fit, and set benefit measures for everything that continues.
After that, run the cycle quarterly and refine it. The first round is always the hardest, because it's the one where projects get stopped.
How Great Minds helps
We design ePMO frameworks sized to the organisation, from lean advisory models for mid-sized businesses to federated models for multi-division enterprises. Because we're an integrator first, we also connect the systems underneath: Jira and Jira Align, Microsoft tools, Salesforce and finance, so the portfolio view is built from live data. See our ePMO framework and consulting service.
Frequently asked questions
What's the difference between a PMO and an ePMO?
A PMO focuses on delivering projects well within one function. An ePMO governs the whole organisation's portfolio of change: which initiatives get funded, how they're prioritised, and whether they deliver their benefits.
Who should an ePMO report to?
To someone with authority over investment decisions across the business, usually the COO, CFO or CEO. Reporting into a single function such as IT tends to limit it to that function's projects.
Is an ePMO only for large enterprises?
No. Organisations with a few hundred staff and several major programs running at once often benefit most, because one failed program has an outsized impact. They usually need a lean model with a small team.
How long does it take to set up?
A working first version, with a portfolio inventory, prioritisation rules and a first decision round, takes about 90 days. Maturing benefits tracking and integrated reporting takes longer.
What replaces Microsoft Project Online?
Project Online retired on 30 September 2026. Microsoft points customers to the new Planner (with Project Plan 3 or 5 for portfolio features), Project Server Subscription Edition, or Dynamics 365 Project Operations. Atlassian's Strategy Collection and Jira Align are the alternatives for organisations whose delivery work already runs in Jira.
Does an ePMO work with agile teams?
Yes, if it governs outcomes, funding and risk rather than dictating method. Portfolio tools such as Jira Align are designed to connect agile team work to strategy and funding.
Where to start
Before designing anything, list every initiative currently in flight and the objective each one supports. If that takes more than a week, or the list surprises the executive team, you've found the case for an ePMO. We're happy to help you build that first view.