Abstract
With the ongoing challenge of successfully managing information technology (IT) projects, organizations are recognizing the need for greater project management discipline. For many organizations, this has meant ratcheting up project management skills, processes, and governance structures by implementing a project management office (PMO). While anecdotal evidence suggests that implementing a PMO can be quite difficult, few studies discuss the specific challenges involved, and how organizations can overcome them. To address this gap in existing knowledge, we conducted a Delphi study to (1) identify the challenges of implementing a PMO for managing IT projects, (2) rank these challenges in order of importance, (3) discover ways in which some organizations have overcome the top-ranked challenges, and (4) understand the role of PMO structure, metrics, and tools in the implementation of a PMO.
We identified 34 unique challenges to implementing a PMO and refined this list to 13 challenges that our Delphi panelists considered most important. The top-three challenges were (1) rigid corporate culture and failure to manage organizational resistance to change, (2) lack of experienced project managers (PMs) and PMO leadership, and (3) lack of appropriate change management strategy. Through follow-up interviews with selected panelists, we identified a series of actions that can be taken to overcome these challenges including having a strong PMO champion, starting small and demonstrating the value of the PMO, obtaining support from opinion leaders, hiring an experienced program manager who understands the organization, bringing the most talented PMs into the PMO implementation team, adopting a flexible change management strategy, and standardizing processes prior to PMO implementation. The interviews were also used to better understand the role of PMO structure, metrics, and tools. In terms of PMO structure, we found that ‘light’ PMOs were more likely to be implemented successfully. Most organizations eschew formal metrics, instead relying on subjective indicators of PMO success. Lastly, it appears that PMO tools are difficult to implement unless a project management culture has been established.
Similar content being viewed by others
References
Aubry M, Hobbs B and Thuillier D (2007) A new framework for understanding organisational project management through the PMO. International Journal of Project Management 25 (4), 328–336.
Aubry M, Hobbs B and Thuillier D (2008) Organisational project management: an historical approach to the study of PMOs. International Journal of Project Management 26 (1), 38–43.
Boyer KK, Olson JR, Calantone RJ and Jackson EC (2002) Print versus electronic surveys: a comparison of two data collection methodologies. Journal of Operations Management 20 (4), 357–373.
Brancheau JC, Janz BD and Wetherbe JC (1996) Key issues in information systems management: 1994-95 sim Delphi results. MIS Quarterly 20 (2).
Brancheau JC and Wetherbe JC (1987) Key issues in information systems management. MIS Quarterly 11 (1), 22–45.
Chang SI and Gable G (2000) Major issues with SAP financials in Queensland government. In Proceedings of the Americas Conference on Information Systems, (CHUNG HM, Ed) pp 972–976, Long Beach, California, USA.
Chrissis MB, Konrad M and Shrum S (2003) CMMI: Guidelines for Process Integration and Product Improvement. Addison-Wesley Professional, Boston, MA.
Christiansen JC and Sherry TC (1992) Project management oversight: a partnership in mass transit projects. Transaction of American Association of Cost Engineers 2, M.4.1–M.4.6.
Couger JD (1988) Key human resource issues in IS in the 1990s: views of IS executives versus human resource executives. Information & Management 14, 161–174.
Crawford JK (2001) The Strategic Project Office: A Guide to Improving Organizational Performance. Marcel Dekker, Inc, New York, NY.
Crawford L (2006) Developing organizational project management capability: theory and practice. Project Management Journal 37 (3), 74–86.
Dai CX (2001) The Role of Project Management Office in Achieving Project Success. George Washington University, Washington, DC.
Dai CX and Wells WG (2004) An exploration of project management office features and their relationship to project performance. International Journal of Project Management 22 (7), 523–532.
Dalkey N and Helmer O (1963) An experimental application of the Delphi method to the use of experts. Management Science 9 (3), 458–467.
Dekleva S and Zupancic J (1996) Key issue in information systems management: a Delphi study in Slovenia. Information and Management 31 (1), 1–11.
Desouza KC and Evaristo JR (2006) Project management offices: a case of knowledge-based archetypes. International Journal of Information Management 26, 414–423.
Dinsmore P (2005) The Right Projects Done Right!: From Business Strategy to Successful Project Implementation. Jossey-Bass, San Francisco, CA.
Doke ER and Swanson NE (1995) Decision variables for selecting prototyping in information systems development: a Delphi study of MIS managers. Information and Management 29, 173–182.
Englund RL, Graham RJ and Dinsmore PC (2003) Creating the Project Office: A Manager's Guide to Leading Organizational Change. John Wiley & Sons, Inc., San Francisco.
Hill GM (2004) Evolving the project management office: a competency continuum. Information Systems Management 21 (4), 45–51.
Hobbs B and Aubry M (2007) A multi-phase research program investigating project management offices (PMOS): the results of phase 1. Project Management Journal 38 (1), 74.
Hobbs B, Aubry M and Thuillier D (2008) The project management office as an organisational innovation. International Journal of Project Management 26 (5), 547–555.
Holsapple P and Joshi K (2002) Knowledge manipulation: results of a Delphi study. Information and Management 39, 477–490.
Kasi V, Keil M, Mathiassen L and Pedersen K (2008) The post mortem paradox: a Delphi study of it specialist perceptions. European Journal of Information Systems 17 (1), 62.
Keil M, Mann J and Rai A (2000) Why software projects escalate: an empirical analysis and test of four theoretical models. MIS Quarterly 24 (4), 631–664.
Keil M and Robey D (2001) Blowing the whistle on troubled software projects. Communications of the ACM 44 (4), 87–93.
Keil M, Tiwana A and Bush A (2002) Reconciling user and project manager perceptions of it project risk: a Delphi study 1. Information Systems Journal 12 (2), 103–119.
Kendall GI and Rollins SC (2003) Advanced Project Portfolio Management and the PMO: Multiplying ROI at Warp Speed. J. Ross Publishing, Boca Raton, FL.
Leemann T (2002) Managing the chaos of change. Journal of Business Strategy 23 (5), 11–16.
Letavec CJ (2006) The Program Management Office: Establishing, Managing and Growing the Value of a PMO. J. Ross Publishing, Fort Lauderdale, FL.
Lincoln YS and Guba EG (1985) Naturalistic Inquiry. Sage Publications Inc., Newbury Park, CA.
Linstone HA and Turoff M (1975) The Delphi Method: Techniques and Applications. Addison-Wesley, Reading, MA.
Liu LL and Yetton PY (2007) The contingent effects on project performance of conducting project reviews and deploying project management offices. IEEE Transactions on Engineering Management, 54 (4), 789–799.
Martin NL, Pearson JM and Furumo K (2007) Is project management: size, practices and the project management office. Journal of Computer Information Systems 47 (4), 52.
Miles MB and Huberman AM (1994) Qualitative Data Analysis. Sage Publications, Thousand Oaks.
Mursu A, Lyytinen K, Soriyan HA and Korpela M (2003) Identifying software project risks in Nigeria: an international comparative study. European Journal of Information Systems 12 (3), 182–194.
Nelms KR and Porter AL (1985) EFTE: an interactive Delphi method. Technological Forecasting and Social Change 28, 43–61.
Norrie J (2008) Breaking Through the Project Fog: How Smart Organizations Achieve Success by Creating, Selecting and Executing On-strategy Projects. John Wiley and Sons, Inc., Mississauga, Ontario.
Okoli C and Pawlowski SD (2004) The Delphi method as a research tool: an example, design considerations and applications. Information & Management 42 (1), 15–29.
Paliwoda SJ (1983) Predicting the future using Delphi. Management Decision 21 (1), 31–37.
PMI (2004) A Guide to the Project Management Body of Knowledge. Project Management Institute, Newtown Square, PA.
Pohlmann T (2003) How Companies Govern Their IT Spending. Forrester Research, Cambridge, MA.
Powell C (2003) The Delphi technique: myths and realities. Journal of Advanced Nursing 41 (4), 376–382.
Rad PF and Levin G (2002) The Advanced Project Management Office: A Comprehensive Look at Function and Implementation. CRC Press, Boca Raton, FL.
Rad PF and Levin G (2003) Is your organization friendly to projects? AACE International Transactions 47, PM.04.1–PM.04.6.
Rad PF and Raghavan A (2000) Establishing an organizational project office. AACE International Transactions 44, PM.13.1–PM.13.9.
Reuvid J (2005) Managing Business Risk: A Practical Guide to Protecting Your Business. Kogan Page, Philadelphia, PA.
Richardson G and Ives B (2004) Systems development processes. Computer 37 (5), 84–86.
Rowe G and Wright G (1999) The Delphi technique as a forecasting tool: issues and analysis. International Journal of Forecasting 15, 353–375.
Rubinstein D (2007) Standish group report: there's less development chaos today. SD Times: Software Development Times on the Web, BZ Media LLC, Huntington, NY.
Santosus M (2003) Office discipline: why you need a project management office. CIO Magazine, International Data Group, Framingham, MA.
Sauer C, Gemino A and Reich B (2007) The impact of size and volatility on it project performance: Studying the factors influencing project risk. Communications of the ACM 50 (11), 79–84.
Schmidt RC (1997) Managing Delphi surveys using nonparametric statistical techniques. Decision Sciences 28 (3), 763–774.
Schmidt RC, Lyytinen K, Keil M and Cule PE (2001) Identifying software project risks: an international Delphi study. Journal of Management Information Systems 17 (4), 5–36.
Stanleigh M (2006) From crisis to control: new standards for project management. Ivey Business Journal (March/April), 1–4.
Thiry M and Deguire M (2007) Recent developments in project-based organisations. International Journal of Project Management 25 (7), 649–658.
Trochim WMK (2001) The Research Methods Knowledge Base. Atomic Dog Publishing, Cincinnati.
Ward JL (2000) Project Management Terms: A Working Glossary. ESI International, Arlington, VA.
Weible R and Wallace J (1998) Cyber research: the impact of the internet on data collection. Marketing Research 10 (3), 19–24.
Wren J (2005) A culture of governance. Ziff Davis Enterprise, New York, NY. eWeek.com.
Xia W and Lee G (2004) Grasping the complexity of is development projects. Communications of the ACM 47 (5), 68–74.
Author information
Authors and Affiliations
Corresponding author
Appendices
Appendix A
See Table A1.
Appendix B
See Figure B1
Appendix C
Semi-structured interview protocol
(1) Overcoming the challenges to PMO
-
How did your organization respond to the top-three challenges to PMO implementation? What worked, or did not work?
(2) PMO structure
-
What was the nature of PMO structure in your organization (PMO-light/PMO-heavy/any other)?
-
Do you think it was an appropriate governance structure? In hindsight, would you recommend any changes to this structure? Is there a governance structure that is more likely to be successful, and where would that be on the PMO-light, PMO-heavy scale?
(3) Metrics for PMO evaluation
-
Has your organization successfully implemented a PMO? Did the organization meet the original objectives of establishing the PMO?
-
Did the implementation of PMO have measurable impacts in terms of project success? How did you measure the impact? What metrics did you use?
(4) PMO tools
-
What project management software or portfolio management applications did you use for PMO implementation? How satisfied are you with those applications in terms of ease of use, functionality, and customizability?
-
Do you consider the PMO tools to be useful devices in pushing change related to PMO implementation?
-
If an organization wants to maximize its chances of success in a PMO implementation, is it better to standardize its processes first before buying one of these tool sets, or after procuring them?
Rights and permissions
About this article
Cite this article
Singh, R., Keil, M. & Kasi, V. Identifying and overcoming the challenges of implementing a project management office. Eur J Inf Syst 18, 409–427 (2009). https://doi.org/10.1057/ejis.2009.29
Received:
Revised:
Accepted:
Published:
Issue Date:
DOI: https://doi.org/10.1057/ejis.2009.29