How is Project Success Affected by Replacing the Project Manager?

  • Tero Vartiainen
  • Maritta Pirhonen

Although replacing the project manager in an on-going project is not uncommon in the IT field, studies on the topic are scarce. In order to increase understanding in this area, we investigated the perceptions of ten experienced project managers on replacement from the perspective of project success. We focused on the critical success factors in the projects, on how the interviewees perceived the replacement of the manager, and on the effects it had. We found that replacing the manager was perceived as an attempt to rescue a troubled project, and as a pertinent part of it, especially in cases in which it strengthened the project process. Replacement was found to affect critical factors such as management and human-relations issues. The results are reflected through the literature, and implications for research and practice are presented.


Project Manager Success Factor Project Success Critical Success Factor Information System Development 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. Aladwani, A.M. 2002. IT project uncertainty, planning and success - An empirical investigation from Kuwait. Information Technology & People, 15, 210-226.CrossRefGoogle Scholar
  2. Belout, A. and Gauvreau, C. 2004. Factors influencing project success: the impact of human resource management. International Journal of Project Management, 22(1), 1-11.CrossRefGoogle Scholar
  3. Blackburn, S. 2002. The project manager and the project-network. International Journal of Project Management, 20(3), 199-204.CrossRefMathSciNetGoogle Scholar
  4. Blake, R.R. and Mouton, J.S. 1978. The New Managerial Grid. Houston: Gulf Publishing Company. Rererenced in F.E. Kast, J.E., Rosenzweig 1985. Or-ganization & Management, A Systems and Contingency Approach. New York: McGraw-Hill.Google Scholar
  5. Boddy, D. 2002. Managing Projects: Building and Leading the Team. Harlow, Essex: Prentice Hall.Google Scholar
  6. Cooke-Davies, T. 2002. The “real” success factors on projects. International Jour-nal of Project Management, 20(3), 185-190.CrossRefGoogle Scholar
  7. Fielding, N. 1993. Qualitative Interviewing. In N. Gilbert (Ed.) Researching So-cial Life. London: SAGE Publications. 135-153.Google Scholar
  8. Hartman, F. and Ashrafi R.A. 2002. Project Management in the Information Sys-tems and Information Technologies Industries. Project Management Journal, 33 (3), 5-15.Google Scholar
  9. Jurison, J. 1999. Software Project Management: the Manager’s View. Communi-cations of Association for Information Systems. Vol 2, Article 17.Google Scholar
  10. Kast, F.E. and Rosenzweig, J.E. 1985. Organization & Management, A Systems and Contingency Approach. New York: McGraw-Hill.Google Scholar
  11. Klein, H.K. and Myers, M.D. 1999. A Set of Principles for Conducting and Evalu-ating Interpretive Field Studies in Information Systems. MIS Quarterly, 23(1), 67-94.CrossRefGoogle Scholar
  12. Kloppenborg, J. and Petrick, T. 1999. Leadership in Project Life Cycle and Team Character Development. Project Management Journal, 30(2), 8-14.Google Scholar
  13. Lee-Kelley, L. and Loong, K.L. 2003. Turner’s Five Functions of Project-Based Management and Situational Leadership in IT Services Projects. International Journal of Project Management, 21(8), 583-591.CrossRefGoogle Scholar
  14. Lyytinen, K. and Hirschheim, R. 1987. Information Systems Failures - A Survey and Classification of the Empirical Literature. Oxford Surveys in Information Technology, vol 4, 257-309.Google Scholar
  15. Maylor, H. 2003. Project Management. Harlow, Essex: Prentice Hall.Google Scholar
  16. Pinto, J. K. and Slevin, D.P. 1988. Project success: Definitions and measurement techniques. Project Management Journal, 19(3), 67-73.Google Scholar
  17. Shenhar, A.J. and Levy, O. 1997. Mapping the Dimensions of Project Success. Project Management Journal, 28 (2), 5-13.Google Scholar
  18. Smith, G.R. 1999. Project Leadership: Why Project Management Alone Doesn’t Work. Hospital Materiel Management Quarterly, Aug1999, 21, 88-92.Google Scholar
  19. Thayer, R. 1987. Software engineering project management: A top-down view. In Tutorial: Software Engineering Project Management, pp. 15-53. IEEE Com-puter Science Press., Los Alamitos, California.Google Scholar
  20. Turner, R. and Müller, R. 2005. The Project Manager’s Leadership Style as a Suc-cess Factor on Projects: a Literature Review. Project Management Journal, 36 (2), 49-61.Google Scholar
  21. Turner, J.R. 1999. The handbook of project-based management. 2nd ed. England: McGraw-Hill Publishing.Google Scholar
  22. Wallace L. and Keil, M. 2004. Software Project Risks and Their Effect on Out-comes. Communications of the ACM, 47(4), 68-73.CrossRefGoogle Scholar
  23. Yeo, K.T. 2002. Critical failure factors in information systems projects. International Journal of Project Management, 20(3), 241-246.CrossRefMathSciNetGoogle Scholar
  24. Yin, K. 1994. Case Study Research, Design and Methods. London: Sage.Google Scholar

Copyright information

© Springer Science+Business Media, LLC 2007

Authors and Affiliations

  • Tero Vartiainen
    • 1
  • Maritta Pirhonen
    • 2
  1. 1.Pori UnitTurku School of EconomicsFinland
  2. 2.Department of Computer Science and Information SystemsUniversity of JyväskyläFinland

Personalised recommendations