| Home- White Paper Index | |
Project Management
Office |
First published April 09 |
Eric Tse |
Rating |
|
This paper discusses the external affairs of Project Management
Offices instead of focusing on the internals. The article was initiated
by the "AtekPC Project Management Office" [1] , Most of the obstacles
to establishing a PMO are beyond the CIO and PMO Manager's control.
There are external factors within the enterprise that will hinder
progress of a PMO implementation.
We are going to take a PMO as a black box, and focus on how the PMO/Program Manager can manage external relations from diplomatic, marketing, public relations, international relations, corporate culture and political perspectives. This involves cooperation between the PMO and other entities in or outside the enterprise, to facilitate a successfully organizational integration.
![]()
By reading the case studies in the "AtekPC Project Management Office" [1], we see a lot of headaches for the CIO when implementation a PMO in the enterprise. Regardless of the technical challenges during the implementation, the core of the problems seems to be that the PMO is lacking organization support, from the top to the bottom. There is not enough executive stakeholder support; there is no visibility of the program; there is a conflict of interests within departments; people are reluctant to change the ways they have been doing things. This paper is going to provide some high level suggestions to improve external relations for the PMO.
![]()
After an in depth study in [1], we can abstract out a few root causes of PMO implementation hindrance.
The PMO vision and role is not clearly defined. There is no complete consensus regarding its purpose, its responsibilities, and its authority. It has slowly evolved.
Not enough executive stakeholder support. Not all of the senior executives were equally enthused about the PMO concept. Authority was primarily being developed bottom-up through the value of the PMO services. Even this was limited to those functional areas and IT areas actively engaging the PMO. There was no current plan to enforce usage at the enterprise level.
Corporate culture limitation. Corporate cultural change had been informal. They never treated PM, PMO, formal processes seriously. Normal Operation Processes and function units have to change their culture, behaviour, and even habits if they work with a PMO.
No support from department management. Department managers may see no value in introducing a PMO in their projects. Also there are political conflicts as well, with managers worrying about the PMO getting to much authority.
Hard to prove value before the PMO can get more support. This is a chicken and egg problem. The senior IT managers encouraged a slow, incremental strategy (baby steps) that would allow the PMO concept to prove itself with small victories won through mentoring one project at a time. While proving themselves, they may fail the challenges of addressing all the cultural limitations and barriers. The PMO had raised issues that had proven too controversial to resolve immediately.
![]()
Teaching the PMO management and CIO to approach and socialize with all the CEO, VPs, CIO, project offices, project managers, resource managers, and other senior executive is beyond the scope of this paper. However this is the very important first step of the whole campaign. In short we can get some insight from PMBOK [17] , Communication Management and Planning.
We need to understand:
There are other aspect like risk identification matrix, procurement plan and change control plan.
Notice getting executive stakeholders support for the project is just like establishing alliances with the countries. Moreover do not limit your PMO by making alliances only with the executives, however getting top management support is a first crucial steps. In an enterprise we can think about making alliances with organizations such as Human Resource, Public Relations, Finance and Audit etc. All these "friendships" will help the PMO to promote itself and facilitate changes throughout the enterprise. We will elaborate on how some of those departments help a PMO implementations.
![]()
You can never reach the top if you don't have a good sales package. Executives are not going to buy your idea. One executive who realises the importance of the PMO is not enough. You need everyone to support you. This paper is not trying to teach the PMO how to be a good sales person. We would like to introduce some add value jargons PMO can use to turn executives on. We will be shallow in this section with literature review that would not touch any details. People can further pull out data from the case studies of the literature to demonstrate the track record of PMO success.
With a more professional and powerful presentations, hopefully you can turn on the executives and gain support from the organization.
![]()
From the case studies, you can see the PMO changes involve everyone in the enterprise. Merely touching the heart of the king(s) is not going to bring you any success. You would like everyone in the company to participate in the change. One thing is to get visibility of the PMO across the enterprise and let people know why we need a PMO. We should consider this as a public relation campaign (PR).
Researching how to organize public relations event is out of the scope of this paper. However departments can learn from the work undertaken when organizations carry out exhibitions and workshops, or even fun fair or charity events to promote what they are doing. Besides demonstrating why we need a PMO and what is a PMO, the important key to success is that everyone in the organization can participate in providing comments for building the framework of the PMO. Therefore they can develop a sense of achievement supporting the PMO implementation.
![]()
We are not going to elaborate too much on this topic. There are a few items worth mentioning:
Instead of merely focusing on changing the ways people have been doing things, PMOs should also try to bring more external support to help local project managers with things they do not know how to do. Hopefully this will help department managers and staff to establish trust with the PMO and gradually gain support from them.
![]()
Creating standards, policies and procedures for a Project Management Office (PMO) is critical to the proper functioning of projects and programs under the PMO and the ultimate success of the PMO within the larger organization. Policies will vary from one organization to another, but most important is understanding the expectations of stakeholders, the needs of the project and program teams and project and program managers and aligning the PMO's mission with the strategic goals of the organization. Please note that this sample Conflict of Interest Policy is for discussion purposes only and that any policy would be required to meet the specific requirements of its governing organization and tailored to meet the specific needs of the PMO and the projects it oversees. [13]
![]()
The executives may need to drive the PMO development along with those strategies in order to solve all these problems. It is more like how to re-engineering the DNA of the corporate. [14]
We need to reprogram the employee while bearing in mind:
Talking about turning staff culture from informal to formal PMO processes implies we need to be professional in understanding behavioural changes. With a significant change in internal processes, just the initial talk of the intended change can be unsettling to a workforce comfortable in its current routine. Process improvement may perfectly achieve their objectives, but the workforce may not be prepared to accept them as part of their daily routines. A behaviour-focused approach makes change sustainable. It helps workers modify the way they feel and think about their jobs by aligning attitudes and behaviours with the system and process changes, as well as with the overall direction of the company. [15]
Also The PMO may want to leverage HR as a strategic partner in helping the organization meet its goals. There are good examples of how HR department can successfully change the corporate culture by launching change program, leveraging leadership approach, managers empowerment and mobilizing people. [16]
![]()
By taking the initiative and implementing the strategies, hopefully the external relations of the PMO can be enhanced and gain top to bottom organization support. In this way the implementation and maintenance of the PMO can be improved.
[1] F. Warren McFarlan, John Hupp, and Mark Kell, (October 2007) The AtekPC Project Management Office, Harvard Business Publishing
[2] Kendall and Rollins, (2003), Project Portfolio Management and the PMO
[ 3] Michael E Thorn, Autumn 2003; Bridge Over Troubled Water: Implementation of a Program Management Office S.A.M. Advanced Management Journal; 68, 4; Global pg. 48
[4] Light, M, (2000). The project office: Teams, processes and tools. Stamford, CT: Gartner Research.
[5] Mark A Johnson; Terry G Joyner; Robert J Martin Jr , ; 2002; Process-driven project management office implementation AACE International Transactions Global pg. PM111
[6] Gerard M Hill, Fall2004, evolving the Project, management office; a competency continuum.
[7] Chris Kaufman, Raghu B. Korrapati, 2007, A PROJECT MANAGEMENT OFFICE (PMO) FRAMEWORK FOR SUCCESSFUL IMPLEMENTATION OF INFORMATION TECHNOLOGY PROJECTS
[8] Brian Hobbs; Monique Aubry, Mar 2007 ; A MULTI-PHASE RESEARCH PROGRAM INVESTIGATING PROJECT MANAGEMENT OFFICES PMOs... Project Management Journal; ; 38, 1; Global pg. 74
[9] Jerry Julian, Julian Advisory Group, Inc, New York, NY, USA, (Sep 2008), How Project Management Office Leaders Facilitate Cross-Project Learning and Cross-Project Learning and Continuous Improvement. 39,3: pg43
[10] Dr. Parviz F. Rad, PE CCE and Dr. Ginger Levin, (2007), Project Management Sophistication and EPM.
[11] Jainendrukumar, (2008), TD. The Project/Program Management Office (PMO). PM World Today. Featured Paper. (Vol. x, Issue I). Retrieved on, 1009
[12] Ruchi Challu. 2009, The quality of global Managers, McClatchy - Tribune Business News. Washington
[13] Author, date, Conflict of Interest Policy, obtained from BU course 646
[14]Diana Mungai and Linda Osgood, 2009, Transforming Culture at the Public Building Services.
[15] Christopher Del Angel, Joe Froelich, Nov 2008, Six Sigma: What went wrong? Customer relationship management.
[16] Per Geisler Hansen , Jakob Soerensen . Strategic HR Review . Chicago: 2009 The Rockwool Group: delivering business growth through culture change . Vol. 8, Iss. 1; pg. 5
[17] author, (2003), Project Management Body of Knowledge (PMBOK), Project Management Institute.
Eric Tse is an international recognized expert/consultant in Enterprise
Access and Identity Management Architecture Design and Implementation.
He has been working with international renowned experts in information
technology in many prestigious companies. He also pursues research
interests in project management, financial models, application/enterprise/solution
architectures, compilation technology and philosophy of science.
![]()
To date, 10 people have rated this article. The average rating is 4.60 - Add your rating. Just select a rating and click the button. No other information required. Only one rating per person is allowed. |
|
|||||||||||||||||||||||||||||||||||
![]()