PJM 6400 Module 5 Final Project: A Report to Executives on a Global Project Management Office Example

A Global PMO for a Four-Site Design Firm: Recommendations to the Executive Committee

Student Name

M.S. in Management in Project Management, Thomas Edison State University

PJM-6400: Global Project Management

Mentor Name

Month Day, Year

A Global PMO for a Four-Site Design Firm: Recommendations to the Executive Committee

To the Executive Committee

This report recommends that the firm establish a global project management office (PMO) to support and standardize how we run client programs across New Brunswick, Galway, Bengaluru and Heredia. It summarizes the problem, recommends a mandate and set of functions, proposes a structure, estimates costs and benefits, and sets out a phased plan with measures.

Executive Summary

Our four sites manage projects in four different ways. What follows is duplicated effort, slow handoffs, fights over people and audit findings; last year these delayed two client programs, and rework, penalties and lost follow-on work cost us about $1.1 million. A global PMO with a supportive and standardizing role, not a controlling one, would own a common methodology, coordinate resources across sites, set common tools and measures and develop our project managers. Its yearly cost of about $780,000 should be recovered within two years. I recommend approving a pilot PMO for new programs starting next quarter, followed by a full rollout over eighteen months. The pilot would cost about $390,000 for its first six months, and I would report results against the measures in this report before asking for the full commitment.

Background

The firm began fifteen years ago as a mechanical design consultancy in New Brunswick serving device makers in the New Jersey corridor. As clients moved toward connected devices and global launches, we acquired a verification laboratory in Galway, a software group in Bengaluru and a stake in a pilot manufacturing partner in Heredia. Revenue has tripled to about $96 million, and 61 percent of our programs now involve at least two sites. Our project management practices did not grow with us. Each acquisition brought capable people and its own habits, and we have never asked them to work in one way. For years this did not matter, because most programs stayed within one site. It matters now, because our clients buy a single program from us and expect a single standard of delivery, whichever site does the work.

The Problem

Over the past three years we have grown from one site to four by acquisition. Each site kept its own way of working. On the infusion pump program, these differences produced three specific problems.

First, inconsistent processes. A client audit found design inputs kept in three different formats and two design reviews held without required attendees. Work passed between sites slowly, since each site expected its own set of documents.

Second, resource conflicts. Engineers report to site managers but work on programs led from New Brunswick. When Galway's site manager reassigned two verification engineers to another client, the pump program lost three weeks.

Third, poor visibility. No one can see, in one place, the status, risks and resource needs of our 23 active programs. Executives learn of problems late, often from clients. Each of these problems shows up in client relationships before it shows up in our own reports.

Options Considered

I considered three alternatives before recommending a PMO.

The first is to do nothing and let each site keep its methods while program managers coordinate informally. This costs nothing new, but it leaves last year's $1.1 million of avoidable costs in place and will get worse as more programs span sites.

The second is a central controlling PMO in New Brunswick, with authority to approve plans, assign resources and stop programs. This would impose consistency quickly, but it would cut across the site managers' authority, and research suggests that PMOs seen as bureaucratic overhead are the ones most often dismantled. Galway and Bengaluru, which have strong local practices, would likely resist it.

The third is a community of practice: project managers from all sites meet regularly to share methods voluntarily. This builds goodwill and costs little, but without ownership of the methodology or the resource process it cannot fix the inconsistencies that caused last year's audit findings.

A supportive and standardizing PMO combines the strengths of the second and third options: it owns the common methodology and governance forums, but it works through site leads and earns its authority by helping programs.

What a PMO Is and What It Should Not Be

Kerzner (2014) describes the PMO as an organization that supports excellence in project management by maintaining the methodology, collecting best practices and lessons learned, supporting project managers and providing information to executives, and he notes that its role has expanded in global companies to include strategic planning and portfolio management.

Research shows that PMOs vary widely and are often short-lived. Hobbs and Aubry (2007) surveyed about 500 PMOs and found great variety in their structures, roles and functions, and that many were questioned or restructured within a few years. The most common functions were monitoring and reporting project performance, developing and implementing a standard methodology, and supporting project managers. Dai and Wells (2004) found that PMO features such as standards and methods, training and consulting support were associated with better project performance.

The lesson for us is that a PMO must be designed for our needs and must earn its place by helping projects, not by adding reporting burden. A controlling PMO that polices project managers would be resisted, especially at sites that already resent central control.

Recommended Mandate

The PMO's mandate would be to help every program at every site succeed by providing a common way of working, coordinating resources, giving executives visibility and developing project managers. It would be a supportive and standardizing PMO: it would set the methodology and tools and run governance forums, but program managers would remain accountable for their programs.

Functions

The methodology, resource council and tools come from earlier analyses; the PMO is the home that keeps them working.

How the Functions Work in Practice

In practice, a program manager starting a new program would meet the site PMO lead in week one to tailor the methodology's plan template, register the program in the portfolio dashboard and request named engineers through the resource view. At each gate, the PMO would schedule the gate review board, check that required deliverables are complete and record decisions in the decision log. Between gates, the PMO would stay out of the way, except to help when a risk is escalated. Each quarter, the PMO would bring site and program managers together in the resource council to balance commitments for the next two quarters, and it would publish the lessons from programs that passed gates or closed. Project managers would see the PMO as the place to get templates, advice and help with conflicts, rather than as an auditor.

What the Sites Told Me

Before writing this report I spoke with each site manager and with six project managers across the four sites. Their views shaped the design. The Galway site manager supported common templates but feared that a PMO would override her verification procedures; the methodology's freedom between gates answers that. The Bengaluru software lead worried that gate reviews would slow agile teams; scheduling gate reviews to coincide with sprint boundaries answers that. The Heredia manufacturing lead asked for earlier involvement in design reviews, which the gate review board will provide. Project managers in New Brunswick asked mainly for help with resource conflicts, which the resource council addresses. Every group asked that the PMO not become another layer of reporting; the single dashboard is designed to replace, not add to, existing reports.

Structure Across Four Sites

A PMO run entirely from New Brunswick would repeat the central control that sites resist. I recommend a hub-and-spoke structure: a small central hub in New Brunswick, led by a PMO director reporting to the chief operating officer, and a PMO lead at each of the three other sites, reporting to the director with a dotted line to the site manager.

Site leads drawn from each site's best project managers would know local practices and earn local trust. This follows the frame-of-mind approach to the matrix from Module 3: the PMO succeeds through cooperation and shared goals, not authority alone.

Culture and Communication

The PMO must work across cultures. Shore and Cross (2005) found that national culture shapes how project participants view authority, planning and uncertainty. The PMO's reporting should make it safe to report bad news early: gate reviews will ask, at each gate, what the team is worried about, and the dashboard will show risks alongside status. Site leads will help adapt training and communication to local expectations while keeping the methodology's core.

Communication will follow the rhythm described in Module 4: a monthly video portfolio review for executives, a biweekly forum for project managers across sites, and a written decision log for methodology changes. Language also matters. English is the working language at every site, but meeting notes and decisions will be written in plain language without idioms, and site leads will check that key messages were understood rather than assume it. Training will use examples from each site, so no site's practice is presented as the only correct one.

Costs

Two of the site leads would come from existing project manager positions, backfilled by promoting senior engineers.

Benefits

If the PMO halves last year's $1.1 million in avoidable costs, it saves $550,000 a year. Added benefits are harder to price but real: faster handoffs between sites, fewer audit findings, earlier warning of problems for executives and better project managers. Most important, our clients increasingly ask in proposals how we manage programs across sites; a PMO with a common methodology answers that question and should help us win larger programs. Winning one additional mid-sized program a year, worth about $3 million in revenue at our typical margin, would add about $450,000, bringing the expected benefit above the cost within two years. There are also benefits for people. Project managers would gain a career path and a community across sites, and engineers would face fewer last-minute reassignments, a frequent complaint in our last engagement survey.

Phased Plan

Starting with new programs avoids disrupting programs midstream, and the pilot gives executives evidence before the full commitment. Changing a program in midstream risks the very delays the PMO is meant to prevent, so programs in progress will adopt the methodology at their next gate, where a natural review point already exists.

Measures of Success

Including project managers' satisfaction matters: Hobbs and Aubry found that PMOs are frequently questioned, and a PMO that its own users value is more likely to survive. Each measure will be reported quarterly, with the method of calculation fixed in advance so results cannot be shaded.

Change Management

Introducing a PMO is itself a change, and the lessons of change management apply. The case for change should be stated in terms the sites feel: lost weeks on the pump program, audit findings that embarrassed every site and clients asking how we manage across borders. Site leads should be chosen from respected project managers, so the PMO is seen as their colleagues rather than headquarters. Early wins matter: the pilot should publish its first portfolio dashboard within six weeks and resolve at least one resource conflict through the council within the first quarter, so that people see the PMO helping. And the executive committee should use the dashboard in its own monthly meetings, because sites will take the PMO seriously only if executives do.

Governance of the PMO

The PMO director would report to the chief operating officer and present a quarterly review to the executive committee covering the measures above and the PMO's own budget. An advisory group of one site manager and two program managers, rotating each year, would review proposed changes to the methodology before they take effect. This keeps the PMO accountable to the people it serves as well as to executives, which research on PMO survival suggests is essential.

Risks

Recommendation

I recommend that the executive committee approve a six-month pilot of a supportive, standardizing global PMO with a hub-and-spoke structure, at an annualized cost of $780,000, beginning next quarter with new programs, and review it against the measures above before approving the full rollout. If the committee approves, I will return in six months with the pilot's results and a decision request for the full rollout, including whether the PMO should take on portfolio planning, the selection and prioritization of programs, which some global firms assign to their PMOs.

Conclusion

Our growth across four countries has outrun our way of running projects. A global PMO would give us one methodology, coordinated resources, common tools and visibility, while respecting the strengths of each site. Designed to support rather than control, and introduced in phases with clear measures, it can pay for itself and position the firm to win the larger global programs our clients now ask us to deliver.

References

Dai, C. X., & Wells, W. G. (2004). An exploration of project management office features and their relationship to project performance. International Journal of Project Management, 22(7), 523-532. https://doi.org/10.1016/j.ijproman.2004.04.001

Hobbs, B., & Aubry, M. (2007). A multi-phase research program investigating project management offices (PMOs): The results of phase 1. Project Management Journal, 38(1), 74-86. https://doi.org/10.1177/875697280703800108

Kerzner, H. (2014). Project management best practices: Achieving global excellence (3rd ed.). Wiley.

Shore, B., & Cross, B. J. (2005). Exploring the role of national culture in the management of large-scale international science projects. International Journal of Project Management, 23(1), 55-64. https://doi.org/10.1016/j.ijproman.2004.05.009