~ By Darrel Raynor and Curt Finch
The potential benefits of a Project Management Office (PMO) are numerous and well-documented. However, many of the benefits never materialise. Take a look at PMOs over the years and you will see that many have restructured, dissolved, or constantly had to justify their existence during both economic downturns as well as high-growth periods. This is evidence enough that PMOs are not yielding demonstrable positive financial results. This churn often causes years of frustration for both the PMOs and the projects and departments they serve. Changing the way in which the PMO is chartered, works, and is perceived within an organisation can ensure that it offers plentiful advantages for the entire organisation.
Let's consider this example: a client forms a PMO to salvage a huge contract with a customer. A very large project lags, causing late deliveries and missed expectations all around. Department staff is not completely honest with the customer, hoping that they will somehow be able to 'catch up.' They fall further behind and an executive is forced to intervene. Experienced senior project managers are brought in to assist with the problem, turn around customer expectations, and evolve communication and estimation processes within three months. In another four months, the project managers turn the projects back over to a grateful department.
The senior project managers who saved the day wonder, "Now what? We had unrestricted executive access; some of the best people across the organisation loaned or transferred to our projects, and spent tens of thousands of dollars on training, equipment, and process improvement. Results were great. Now we can't get a phone call returned from a director outside the PMO or any attention to the best practices we just proved are necessary to keep projects out of the red zone." Three of the four project managers are let go or quit within the next six months along with half of the PMO staff of 20.
This example is not just for illustration - it is happening in organisations all across the country every day. If the PMO is helpful in solving the big problem, then PMO staff members must assume other roles to continue to justify their existence. When PMOs define their own course, the high-percentage outcome is stagnated by over-regulation and process. It does not take long for your PMO to lose power and possibly be disbanded.
Strategies to remain financially viable:
Let's look at another example: a large organisation takes a hit in their most recent audit for compliance in regards to Sarbanes-Oxley and internal policy governance requirements, which affects the organisation's financials. The projects in violation include IT projects as well as others. Several direct reports of the COO band together to 'review the situation' that a now out-of-favour peer has gotten their department into.
They recommend many process changes at a high-level that go something like this, "They should have done this, this, this, and that." No one considers or estimates the amount of effort (person hours), training or persuasive change management required to move the entire staff to a phase-gate approval process. (A phase-gate approval process requires that at the end of every phase, the project manager prepares a project status report and submits it to senior management to get approval to move on to the next phase of the project.) A project is chartered, training is authorised, tools are purchased and installed (not implemented, just installed), and a set of directives comes down to the PMO, not the departments, to get cracking.
At this point, department heads and their direct reports begin a campaign to undermine PMO authority which is quickly degrading. Eventually, the PMO is disbanded and the PMO director is fired for "not being able to work with his peers." The organisation's compliance is upgraded from a complete failure to spotty (at best), which requires a good deal of convincing.
Financially, a PMO tasked with making other departments comply with vague or second-hand demands is destined to fail. PMOs in this position can be misused as merely lip service providers for governance coverage required by Sarbanes-Oxley, FDA, and other regulatory, investor and customer requirements.
Strategies to remain financially viable:
The difficulty in demonstrating real value from the PMO is twofold. First, traditional financial measurements of PMO success do not usually provide immediate, tangible benefits. There are many simple metrics that can be used to show the number of projects being completed on time and within budget. However, this data can be misleading. A possibly misconstrued metric would be, "we have never brought a $10 million dollar project in on time or within budget." On the surface, that may sound irresponsible. In reality, it is due to an unrealistic plan and lack of deeper collaboration with project sponsors, executives and teams on all of the project's dimensions, which are more than just time and money.
Second, the assigned role of the PMO in a given organisation might not be appropriate, and can ultimately serve as an impediment to the execution of projects if not employed correctly. As seen in the second problem scenario above, PMOs that act as a regulatory force without clear directives and sponsorship from senior executives only make the project manager's job more difficult.
How can you use your PMO in a way that maximises its potential and improves your organisation's ROI?
The groundwork for a successful PMO actually begins at the top. A PMO requires sponsorship from upper-level management (read: C-suite level executives) in order to build and maintain a presence across the organisation with the flexibility required to address various important project management issues. Allowing the PMO to do its job with executive backing will empower the PMO to address widespread issues quickly and effectively.
There is no set-in-stone way to implement a PMO. Rather, it should be organised and supported in ways that address the organisation's specific issues. When considering where to go with a PMO, an organisation should ask the simple question, "What problems prompted the creation of the PMO in the first place?" Assign the PMO to those tasks, and extend its reach as necessary to enable smooth operations.
There are three metrics commonly used to determine the effectiveness of a PMO at any given time. These are:
Improvement in each of these three categories is a good indicator that the PMO is working smoothly and to the best financial interest of the organisation.
As more and more projects are supported by the PMO, specific patterns in project execution will emerge and its predictive accuracy will increase. In this way, the PMO is constantly self-improving and will eventually become a cost-saving nexus of efficiency within your organisation.
¹ Santosus, Megan (2003) Why You Need a Project Management Office (PMO)
Darrel Raynor is a senior technology executive, consultant and turnaround specialist with over 20 years leadership experience streamlining operations, systems, people and projects. He increases margin and profit, and decreases organisation friction internally and externally with customers, vendors and partners. He is author of the forthcoming book, "Agile & Integrate Project Management" and writes The Management Advisor column to help raise readers' effectiveness. He holds the Project Manager Professional (PMP) certification and an MBA in Information Systems, Managing Advanced Technologies from Golden Gate University in San Francisco.
Curt Finch is the CEO of Journyx. Since 1996, Journyx has remained committed to helping customers intelligently invest their time and resources to achieve per-person, per-project profitability. Curt earned a Bachelor of Science degree in Computer Science from Virginia Tech in 1987. As a software programmer fixing bugs for IBM in the early '90s, Curt Finch found that tracking the time it took to fix each bug revealed the per-bug profitability. Curt knew that this concept of using time-tracking data to determine project profitability was a winning idea and something that companies were not doing - yet. Curt created the world's first web-based timesheet application and the foundation for the current Journyx product offerings in 1997. Curt is an avid speaker and writer. Learn more about Curt at Journyx