Vague project start makes project success of outsourced software development projects uncertain
Pages 351 - 365
Abstract
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.
References
[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).
[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).
[3]
ISO/IEC, ed.: ISO/IEC 12207-2008: Systems and software engineering -- Software life cycle processes. ISO/IEC, Geneva, Switzerland (2008).
[4]
Cooke-Davies, T.: The "real" success factors on projects. International Journal of Project Management 20, 185-190 (2002).
[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).
[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).
[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).
[8]
Fangel, M.: Planning project start-up. International Journal of Project Management 2, 242-245 (1984).
[9]
Egginton, B.: The project start-up process -- getting it to work better. Engineering Management Journal 6, 88-92 (1996).
[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).
[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).
[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).
[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).
[14]
ISO/IEC, ed.: ISO/IEC 15288-2008: Systems and software engineering -- System life cycle processes. ISO/IEC, Geneva, Switzerland (2008).
[15]
ISO/IEC, ed.: ISO/IEC 15504: Information Technology -- Process Assessment. ISO/IEC, Geneva, Switzerland (2004).
[16]
ISO/IEC, ed.: ISO/IEC 16085: Systems and software engineering -- Life cycle processes -- Risk management. ISO/IEC, Geneva, Switzerland (2006).
[17]
ISO/IEC, ed.: ISO/IEC 16326: Systems and software engineering -- Life cycle processes -- Project management. ISO/IEC, Geneva, Switzerland, Final Draft (2009).
[18]
ProjectManagement Institute, ed.: A Guide to the Project Management Body of Knowledge, 3rd edn. Project Management Institute, Pennsylvania, USA (2004), ANSI/PMI 99-001-2004
[19]
Sommerville, I.: Software Engineering, 8th edn. Pearson Education Limited, London (2007).
[20]
Pressman, R.S.: Software Engineering: A Practitioner's Approach, 6th edn. McGraw-Hill, New York (2005).
[21]
Royce, W.: Software project management: a unified framework. Addison-Wesley Longman, Inc., Amsterdam (1998).
[22]
Torp, O.: Efficient project start-up (2003), http://www.concept.ntnu.no/attachments/058_2004_johanesen_ nordnett_efficientprojectstart_up_torp.pdf, Unpublished paper (accessed January 4, 2010).
[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).
[24]
Haapio, T., Ahonen, J.J.: A case study on the success of introducing general nonconstruction 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).
Index Terms
- Vague project start makes project success of outsourced software development projects uncertain
Index terms have been assigned to the content through auto-classification.
Recommendations
When did your project start? - The software supplier's perspective
We study software development projects in supplier firms.Project managers assign a project start date differently even within one company.A project may lose knowledge, profitability, and be late before its start.We suggest definitions related to project ...
Agile software development projects–Unveiling the human-related critical success factors
Highlights- We examine the human factors that contribute to agile software development success.
- Team capability has a strong effect on the success of agile software development.
- Customer involvement has a strong effect on the success of agile ...
Abstract ContextInvestment in information technology is associated with better business performance when its implementation is successful, but it has high costs in case of failure, especially for large software development projects, which typically have ...
Identifying key success factors for globally distributed software development project using simulation: a case study
ICSP'08: Proceedings of the Software process, 2008 international conference on Making globally distributed software development a success storyWith the increased pressure to reduce cost, reduce development time,and improve quality, many software companies are moving toward using aGlobally Distributed Software Development (GSD) paradigm. Due to the challengesand difficulties with GSD, ...
Comments
Please enable JavaScript to view thecomments powered by Disqus.Information & Contributors
Information
Published In
Publisher
Springer-Verlag
Berlin, Heidelberg
Publication History
Published: 21 June 2010
Qualifiers
- Article
Contributors
Other Metrics
Bibliometrics & Citations
Bibliometrics
Article Metrics
- 0Total Citations
- 0Total Downloads
- Downloads (Last 12 months)0
- Downloads (Last 6 weeks)0
Reflects downloads up to 21 Dec 2024