Are PMOs becoming obsolete in agile organizations, or can they reinvent themselves as strategy accelerators?

Lissette Indhira Pimentel Sosa
This is a timely and essential question, one that many organizations are struggling to answer in practice, not just theory.

The truth is: PMOs aren’t becoming obsolete.
Traditional PMOs are.

We’re not witnessing the “death” of the PMO, we’re witnessing the evolution of its DNA.

If a PMO’s core identity is rooted in control, approvals, and templated reporting, then yes it risks irrelevance in fast-moving environments.
But if it repositions itself as a Value & Learning Office, aligning portfolios with strategic intent and enabling intelligent flow of information, it becomes indispensable.

I've seen this shift in practice through:

- From Project Governance to Outcome Enablement
- From Reports for Control to Insights for Decision-Making
- From Gatekeepers to Sensemakers
- From Templates to Toolkits

And when PMOs start tracking metrics like Time-to-Value, Decision Latency, or % Strategic Alignment, they don't just report, they enable decisions.

My take: The PMO isn’t dead, it’s becoming something more powerful: a Strategy Accelerator with Systems Intelligence.

Are you seeing this transformation in your context?
Or is resistance still slowing the shift?

I’d say reinvention, not decline. Traditional, compliance-heavy PMOs may fade, but strategy-focused, adaptive PMOs are gaining importance. By shifting from controlling to enabling, through data-driven insights, lightweight governance, and aligning portfolios with strategy, PMOs can become accelerators of value delivery instead of bottlenecks.

If you want a deeper look into scaling the PMO, I recommend the book "From PMO to VMO - Managing for Value Delivery" (2021, by Sanjiv Augustine et al.) for more information on a direction you could take and things to consider along the way. You may not need to structure your VMO the same as described in the book (it is geared toward SAFe, which doesn't work for every company, for varying reasons), but it does highlight key elements to put in place, from processes to concepts, that will help the PMO measure and deliver value.

The PMO Value Ring, now PMOCP, spoke to the increasing need for PMOs to understand the value the business stakeholders need and to intentionally adjust the things the PMO monitors and drives according to those needs - to stay relevant. If business needs are changing, it makes sense for the PMO to adapt if it wants to continue to exist.

I think that a concept that has been lost is that the PMO wasn’t originally meant to be rigid. Early literature framed it as a support-and-control function, but by the mid-2000s, researchers like Hobbs and Aubry were showing that PMOs are inherently fluid — temporary organizational experiments that shift with business needs. The perception of PMOs as bureaucratic comes more from how companies implemented them, not from their roots. As such, I feel that what we're seeing, in some cases, is the return of the PMO to its original intent.

When it comes to scaling agile, we're also seeing the PMO, as an organization, disappear in some companies. This isn't necessarily a bad thing. LeSS downplays the role of the PMO. DA suggests Lean Governance bodies. Scrum@Scale and Nexus don't have a formal PMO concept - they expand Scrum's core roles. The PMO may be gone, but the value-adding processes are still there. We, as Project Managers, may want a Project Management Office because it helps define who we are and creates the illusion of permanence, but if that's all it is, what's the point? We should, instead, be concerned with whether the appropriate processes and governance are in place to be able to measure the things that matter and respond quickly and effectively to changing business needs, even when the business isn't sure what it needs. That last statement may sound like hubris, but I've heard multiple examples of companies forming a PMO because they "need a PMO" and then the people involved in the new PMO start figuring out what they need to do - there was no mandate for specific problems to solve. To be honest, I did get a job this way, once, so I can't complain too much, except for the fact that we became a figurehead instead of enablers of real change and value delivery.