Is the concept of the PMO obsolete?
Just read this eye opening report from the Projects At Work site on the Hackett Group’s research results on the decline of the PMO. There’s a quote from the principal researcher named John Reeves, which could read like a summary of my conclusions on the reality check needed regarding the centralization of the PMO that I posted back on September 2012:
“Since the recession, many companies have simply given up on PMOs. And with good reason,” said The Hackett Group IT Advisory Practice Leader John Reeves. “The way most companies implement PMOs, they have become large bureaucratic organizations with myopic viewpoints. Too often they focus on practices that simply create a drag on the organization, facilitate design weaknesses, increase complexity and drive up maintenance and support costs. It’s a shame, because the paradox is that our research also shows that when used properly, PMOs can be exceptionally effective at driving quality and reducing complexity. That’s why they’re a key best practice at virtually every world-class IT organization we’ve studied.”
I’ve been involved with a few of these kinds of PMOs and I’ve yet to see it at the world class level discussed by Mr. Reeves, though that’s not saying they don’t exist. I just haven’t personally witnessed one, though to be fair I’ve seen some instances of it working well in certain situations especially if there was sound executive support.
The rest of the report outlines some pretty dismal results and statistics regarding the decline of the PMO in the IT sector (where currently it is utilized the most):
The Hackett Group’s research found that companies with low PMO utilization actually see 32 percent lower operating costs than companies with high PMO utilization.
The study also found that high PMO utilization did not drive better business outcomes or project delivery performance. Companies with high PMO usage showed virtually identical ability to deliver projects on-time or on-budget. They also showed virtually identical ability to achieve anticipated benefits, achieve stated ROI targets, and deliver to specifications.
PMO usage has been on the decline since 2009, the study also found. The percent of infrastructure projects managed by PMOs has dropped by over 20 percent, while its use for application projects has dropped by nearly 18 percent. Overall, only 53 percent of all IT projects are currently managed by PMOs, down nearly 12 percent points since 2009. The size of PMOs has also been shrinking, according to The Hackett Group’s study, with the average number of FTEs dedicated to PMO activities falling by 41 percent from 2009 to 2011. On a relative basis, FTEs dedicated to PMO activities dropped from 6% of total IT staff in 2009 to just 2% in 2011.
So what this report shows is that PMO’s with high utilization rates actually increase costs, did not produce better business outcomes or project delivery and has been on the decline since 2009. So why even bother with implementing a PMO?
The report outlines 4 key strategies to buck this trend which includes:
- Centralized IT demand management
- Accountability for business benefits
- Standardization of processes and architecture
- Program and project reviews
According to the Hackett Group, these “practices enable world-class IT organizations to effectively utilize PMOs to drive IT complexity reduction, improve ROI, and more frequently deliver projects on time and on budget.” Though the report gives some general statistics claiming that PMO’s that have adopted the 4 strategies are four times as likely to achieve their ROI (I’d like to know what these are) targets as well as “63 percent more likely to deliver projects on time and on budget”, it is very light on these details unlike the details about the dismal results and decline of the PMO’s.
Though you’d have to take the report with a grain of salt since they are an IT consulting and advisory group that will no doubt come in to help your organization achieve the four strategic buck busting trends, my own experiences, as well as anecdotal evidence and speaking personally with real world project and portfolio managers from within and outside organizations I’ve been involved with, seem to indicate that the inability of the PMOs to realize their benefits and their gradual decline over the years is real.
So what’s the solution? I’m not sure, but I think the first step is to realize that the traditional model of the PMO needs to get seriously reevaluated, revised, then field tested to make sure it works. It will be interesting to see how this evolves.
I’ve been on the creation and continued management of PMOs in both IT and the Design professions. In its current configuration by PMI, the PMO creates overhead and little, if any value. Therefore, RIP PMO.
In it’s place we are finding multidisciplinary teams of cross functional members who respond to needs of departments far more effective. This can be implemented as part of an IT action, or from the CEO office. I prefer to see IT and design teams as support and implementation catalysts rather than responsible for the definition of projects and their requirements. Key stakeholders are often much better at doing this when aided by a practiced listener and implementer. aa
Thanks Andrew for your reply. What your outlining sounds close to what people in the Agile world are calling a agile based PMO or Agile PMO. It’s yet to be seen if this pans out, but your suggestions are pretty good.
Deeply evaluating the recent IT based PMOs issues/trends of strategic-misalignment, under/over design, implementation and operational after-facts; my humble opinion is that those PMOs are not going to be obsolete …… but going to the next level of maturity “being merged and/or integrated in other business processes”. The same phenomena I have personally experienced (and now advocating) in my past PMO endeavors. Many classical examples are in: Oil & Gas, Mining, Defense and IT Industries with practicing large firms like: Shell Chemicals/BAE systems/Saudi Aramco/IBM/ORANGE/CISCO etc… The start-to-end PMO activities are now basically merged, integrated, and shared by other business processes. So naturally IT PMOs are experiencing that transformation to maturity!!! History repeats its self, those Construction/Defense/Manufacturing etc… type PMOs did the same.
Hi Khalid,
Thanks for your reply. I just wrote a follow up post on this topic and IMHO, while I agree that the core concept of the PMO is not obsolete, the idea of implementing it in a functional organization is. This is because the majority of PMOs seem to be deployed in large functional based organizations. For these functional departments, their operational priorities usually trumps your project needs and when there’s a conflict between moving resources to your high priority project or to put out operational fires, this will cause a conflict. It doesn’t seem to me that this was well thought out.
On another point, I think your idea of IT trending towards being merged with normal business processes is correct, but this also highlights that IT is no longer becoming a strategic advantage and “just another” cost center and services needed to support business in general. I’m not so sure for those in IT if this is what is desired.
[…] of connecting strategy to projects and ensuring high success rates. Malgorzata: Do you agree with Don Kim that the traditional model of the PMO needs to get seriously re-evaluated, revised, then field […]