Management Principles Associated With IT Project Success

Success in information technology (IT) projects remains elusive, even after decades of efforts to improve it. Most of these efforts have focused on variations of the traditional project management paradigm as promulgated by PMBOK. We suspected that a potential cause of high IT project failure is with the paradigm, which focuses on the project itself and on meeting time and cost targets. A new paradigm called Value-Driven Change Leadership (VDCL) originated from discussions of a panel of project management experts. This paper describes the principles of that paradigm. It also reports the results from a survey of four project managers on the association between project success and management principles from VDCL and PMBOK.

[1]  Jack J. Phillips,et al.  The Project Management Scorecard: Measuring the Success of Project Management Solutions , 2002 .

[2]  A. Shenhar,et al.  The relative importance of project success dimensions , 1997 .

[3]  M M O'Connor,et al.  Quality projects in the 1990s: a review of past projects and future trends , 1992 .

[4]  Terry Cooke-Davies,et al.  The “real” success factors on projects , 2002 .

[5]  AGILE DEVELOPMENT : LESSONS LEARNED FROM THE FIRST SCRUM , 2004 .

[6]  Henry C. Lucas,et al.  Why information systems fail , 1975 .

[7]  Detmar W. Straub,et al.  Specifying Formative Constructs in Information Systems Research , 2007, MIS Q..

[8]  Amrit Tiwana,et al.  The one-minute risk assessment tool , 2004, CACM.

[9]  Paul A. Tedesco.  Common Sense in Project Management , 2006 .

[10]  Blaize Horner Reich,et al.  The impact of size and volatility on IT project performance , 2007, CACM.

[11]  Tony Murphy,et al.  Achieving Business Value from Technology: A Practical Guide for Today's Executive , 2002 .

[12]  Jonas Söderlund,et al.  Reinventing project management, by Aaron Shenhar a Dov Dvir , 2008 .

[13]  Erling S. Andersen,et al.  Goal Directed Project Management: Effective Techniques and Strategies , 1998 .

[14]  Stuart E. Madnick,et al.  The elusive silver lining: how we fail to learn from failure in software development , 2011 .

[15]  Magne Jørgensen,et al.  How large are software cost overruns? A review of the 1994 CHAOS report , 2006, Inf. Softw. Technol..

[16]  Elizabeth Daniel,et al.  Benefits management : delivering value from IS & IT investments , 2005 .

[17]  John M. Nicholas.  Project Management for Business Engineering and Technology , 2011 .

[18]  Robert L. Glass.  Computing Calamities: Lessons Learned from Products, Projects, and Companies That Failed , 1998 .

[19]  Justus D. Naumann,et al.  Empirical investigation of systems development practices and results , 1984, Inf. Manag..

[20]  Brian Randell,et al.  Software engineering : report on a conference sponsored by the NATO Science Committee, Garmisch, Germany, 7th to 11th October 1968 , 1969 .

[21]  B. Randell,et al.  Software Engineering: Report of a conference sponsored by the NATO Science Committee, Garmisch, Germany, 7-11 Oct. 1968, Brussels, Scientific Affairs Division, NATO , 1969 .

[22]  Alistair Cockburn,et al.  Agile Software Development , 2001 .

[23]  J. Kelly,et al.  Managing Value as a Management Style for Projects , 2007 .

[24]  M. Weisbord,et al.  Future Search: An Action Guide to Finding Common Ground in Organizations and Communities , 1995 .

[25]  Judith C. Kingstone,et al.  Managing at the Speed of Change , 1998 .

[26]  Brian Randell,et al.  Software Engineering: As it was in 1968 , 1979, ICSE.

[27]  Roger Atkinson,et al.  Project management: cost, time and quality, two best guesses and a phenomenon, its time to accept other success criteria , 1999 .

[28]  Jan Terje Karlsen,et al.  Perspectives on project management , 2007 .

[29]  Anton de Wit,et al.  Measurement of project success , 1988 .

[30]  Kweku Ewusi-Mensah,et al.  Software development failures : anatomy of abandoned projects , 2003 .

[31]  B. N. Baker,et al.  Factors Affecting Project Success , 2008 .

[32]  Edward Yourdon,et al.  Death March , 1997 .