Vague Project Start Makes Project Success of Outsourced Software Development Projects Uncertain

A definition of a project success includes at least three criteria: 1) meeting planning goals, 2) customer benefits, and 3) supplier benefits. This study aims to point out the importance of the definition of the project start, the project start date, and what work should be included in the project effort in order to ensure the supplier's benefits. The ambiguity of the project start risks the profitability of the project and therefore makes project success at least from supplier's point of view uncertain. Moreover, vague project start makes it more difficult to compare project management metrics, such as duration and effort, between projects. There is no clear definition for the project start either in literature or practice. Based on interviews, the definitions are provided for project start, project start date, and project start-up effort included in the project.

[1]  Morten Fangel.  Planning project start-up , 1984 .

[2]  A. K. Munns,et al.  The role of project management in achieving project success , 1996 .

[3]  Walker Royce,et al.  Software Project Management: A Unified Framework , 1998 .

[4]  J. R. Turner,et al.  Goals-and-methods matrix: coping with projects with ill defined goals and/or methods of achieving them , 1993 .

[5]  Johannes I.M. Halman,et al.  Evaluating effectiveness of project start-ups: an exploratory study , 2002 .

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

[7]  Peter Haried,et al.  Evaluating the Success in International Sourcing of Information Technology Projects: The Need for a Relational Client-Vendor Approach , 2009 .

[8]  Jarmo J. Ahonen,et al.  A Case Study on the Success of Introducing General Non-construction Activities for Project Management and Planning Improvement , 2006, PROFES.

[9]  Morten Fangel.  To start or to start up , 1991 .

[10]  Tridas Mukhopadhyay,et al.  Software Project Duration and Effort: An Empirical Study , 2002, Inf. Technol. Manag..

[11]  Ian Sommerville,et al.  Software Engineering, 8. Auflage , 2007, it : Informatik.

[12]  Stuart Anderson,et al.  Requirements Evolution from Process to Product Oriented Management , 2001, PROFES.

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

[14]  Marjorie J. Cooper,et al.  Tying the pieces together: A normative framework for integrating sales and project operations , 2007 .

[15]  B. Egginton.  The project start up process-getting it to work better , 1996 .

[16]  Lynn Crawford,et al.  Fundamental uncertainties in projects and the scope of project management , 2006 .

[17]  Tzvi Raz,et al.  An empirical analysis of the relationship between project planning and project success , 2003 .

[18]  Jim Abraham,et al.  Review of Software project management: A unified framework by Walker Royce, Addison-Wesley Longman, Inc., Reading, MA, 1998 , 2000 .

[19]  Roger S Pressman.  Software Engineering: A Practitioner's Approach with Bonus Chapter on Agile Development , 2003 .

[20]  Ken Lynch,et al.  Project Management Institute (PMI) , 2004 .