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

  • Paula Savolainen
Part of the Lecture Notes in Computer Science book series (LNCS, volume 6156)


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.


Project Management Start Date Software Project Project Success Project Work 
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. 1.
    Dvir, D., Raz, T., Shenhar, A.J.: An empirical analysis of the relationship between project planning and project success. International Journal of Project Management 21, 89–95 (2003)CrossRefGoogle Scholar
  2. 2.
    Atkinson, R.: Project management: cost, time and quality, two best guesses and a phenomenon, it’s time to accept other success criteria. International Journal of Project Management 17, 337–342 (1999)CrossRefGoogle Scholar
  3. 3.
    ISO/IEC, ed.: ISO/IEC 12207-2008: Systems and software engineering — Software life cycle processes. ISO/IEC, Geneva, Switzerland (2008)Google Scholar
  4. 4.
    Cooke-Davies, T.: The “real” success factors on projects. International Journal of Project Management 20, 185–190 (2002)CrossRefGoogle Scholar
  5. 5.
    Munns, A.K., Bjeirmi, B.F.: The role of project management in achieving project success. International Journal of Project Management 14, 81–87 (1996)CrossRefGoogle Scholar
  6. 6.
    Haried, P., Ramamurthy, K.: Evaluating the success in international sourcing of information technology projects: The need for a relational client-vendor approach. Project Management Journal 40, 56–71 (2009)CrossRefGoogle Scholar
  7. 7.
    Cooper, M.J., Budd, C.S.: Tying the pieces together: A normative framework for integrating sales and project operations. Industrial Marketing Management 36, 173–182 (2007)CrossRefGoogle Scholar
  8. 8.
    Fangel, M.: Planning project start-up. International Journal of Project Management 2, 242–245 (1984)CrossRefGoogle Scholar
  9. 9.
    Egginton, B.: The project start-up process — getting it to work better. Engineering Management Journal 6, 88–92 (1996)CrossRefGoogle Scholar
  10. 10.
    Turner, J.R., Cochrane, R.A.: Goals-and-methods matrix: coping with projects with ill defined goals and/or methods of achieving them. International Journal of Project Management 11, 93–102 (1993)CrossRefGoogle Scholar
  11. 11.
    Barry, E.J., Mukhopadhyay, T., Slaughter, S.A.: Software project duration and effort: An empirical study. Information Technology and Management 3, 113–136 (2002)CrossRefGoogle Scholar
  12. 12.
    Atkinson, R., Crawford, L., Ward, S.: Fundamental uncertainties in projects and the scope of project management. International Journal of Project Management 24, 687–698 (2006)CrossRefGoogle Scholar
  13. 13.
    Fangel, M.: To start or to start-up?: That is the key question of project initiation. International Journal of Project Management 9, 5–9 (1991)CrossRefGoogle Scholar
  14. 14.
    ISO/IEC, ed.: ISO/IEC 15288–2008: Systems and software engineering — System life cycle processes. ISO/IEC, Geneva, Switzerland (2008)Google Scholar
  15. 15.
    ISO/IEC, ed.: ISO/IEC 15504: Information Technology — Process Assessment. ISO/IEC, Geneva, Switzerland (2004)Google Scholar
  16. 16.
    ISO/IEC, ed.: ISO/IEC 16085: Systems and software engineering — Life cycle processes — Risk management. ISO/IEC, Geneva, Switzerland (2006)Google Scholar
  17. 17.
    ISO/IEC, ed.: ISO/IEC 16326: Systems and software engineering — Life cycle processes — Project management. ISO/IEC, Geneva, Switzerland, Final Draft (2009)Google Scholar
  18. 18.
    Project Management Institute, ed.: A Guide to the Project Management Body of Knowledge, 3rd edn. Project Management Institute, Pennsylvania, USA (2004), ANSI/PMI 99-001-2004Google Scholar
  19. 19.
    Sommerville, I.: Software Engineering, 8th edn. Pearson Education Limited, London (2007)zbMATHGoogle Scholar
  20. 20.
    Pressman, R.S.: Software Engineering: A Practitioner’s Approach, 6th edn. McGraw-Hill, New York (2005)Google Scholar
  21. 21.
    Royce, W.: Software project management: a unified framework. Addison-Wesley Longman, Inc., Amsterdam (1998)Google Scholar
  22. 22.
    Torp, O.: Efficient project start-up (2003),, Unpublished paper (accessed January 4, 2010)
  23. 23.
    Halman, J.I.M., Burger, G.T.N.: Evaluating effectiveness of project start-ups: an exploratory study. International Journal of Project Management 20, 81–89 (2002)CrossRefGoogle Scholar
  24. 24.
    Haapio, T., Ahonen, J.J.: A case study on the success of introducing general non-construction activities for project management and planning improvement. In: Münch, J., Vierimaa, M. (eds.) PROFES 2006. LNCS, vol. 4034, pp. 151–165. Springer, Heidelberg (2006)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2010

Authors and Affiliations

  • Paula Savolainen
    • 1
    • 2
  1. 1.School of ComputingUniversity of Eastern FinlandKuopioFinland
  2. 2.Lero — The Irish Software Engineering Research CentreUniversity of LimerickIreland

Personalised recommendations