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 start and project start date.We emphasise the need to study software development projects in a business context. A software development project may be considered a failure because it is late. In order to be able to assess this, a project start date should be known. The purpose of the paper is to study software development projects in a business context and especially project start from the supplier's perspective. In our research, we observed different ways of assigning project start but did not observe any company-level instructions for defining it. We raise questions regarding knowledge loss, project profitability, and having a project running late even before the project has started. We provide definitions for project start and project start date, and define boundaries for software supplier's project start-up. With this paper, we emphasise the need to study software development projects in a business context. The paper contributes to research on project management success, the software project business, and the management of a software project in a business context.

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

[2]  Dag I. K. Sjøberg,et al.  The impact of customer expectation on software development effort estimates , 2004 .

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

[4]  Bandula Jayatilaka,et al.  Information systems outsourcing: a survey and analysis of the literature , 2004, DATB.

[5]  B. Cova,et al.  How to create competitive advantage in project business , 1993 .

[6]  Robert L. Glass,et al.  Loyal Opposition - Frequently Forgotten Fundamental Facts about Software Engineering , 2001, IEEE Softw..

[7]  Paul L. Bannerman,et al.  Risk and risk management in software projects: A reassessment , 2008, J. Syst. Softw..

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

[9]  Kalle Lyytinen,et al.  Identifying Software Project Risks: An International Delphi Study , 2001, J. Manag. Inf. Syst..

[10]  M. Zedtwitz.  Organizational Learning through Post-project Reviews in R&D , 2002 .

[11]  June M. Verner,et al.  Why did your project fail? , 2009, Commun. ACM.

[12]  Henrikki Tikkanen,et al.  Relationships and project marketing success , 2002 .

[13]  Risto T. Salminen,et al.  Changing Project Business Orientations: Towards a new Logic of Project Marketing , 2010 .

[14]  Audris Mockus,et al.  Variability and Reproducibility in Software Engineering: A Study of Four Companies that Developed the Same System , 2009, IEEE Transactions on Software Engineering.

[15]  Wynne W. Chin,et al.  Information systems outsourcing relationship factors: detailed conceptualization and initial evidence , 2005, DATB.

[16]  Magne Jørgensen,et al.  An empirical study of software project bidding , 2004, IEEE Transactions on Software Engineering.

[17]  Jarmo J. Ahonen,et al.  Knowledge lost: Challenges in changing project manager between sales and implementation in software projects , 2015 .

[18]  June M. Verner,et al.  What Happens Before a Project Starts? - Project Start-up from the Supplier Perspective , 2010, ISD.

[19]  Alton Yeow-Kuan Chua,et al.  Exhuming it Projects from Their Graves: An Analysis of Eight Failure Cases and Their Risk Factors , 2009, J. Comput. Inf. Syst..

[20]  Barbara A. Kitchenham,et al.  Modeling Software Bidding Risks , 2003, IEEE Trans. Software Eng..

[21]  Sönke Albers,et al.  Pipeline management for the acquisition of industrial projects , 2010 .

[22]  Mauri Laitinen,et al.  Thinking objectively: software engineering in the small , 2000, CACM.

[23]  Karlos Artto,et al.  A Negotiation Approach to Project Sales and Implementation , 2007 .

[24]  Karlos Artto,et al.  Organizing in the Context of Global Project-based Firm The Case of Sales-Operations Interface , 2013 .

[25]  June M. Verner,et al.  Defining and contributing to software development success , 2006, CACM.

[26]  Mary Sumner,et al.  Exploring the Linkage Between the Characteristics of it Project Leaders and Project Success , 2006, Inf. Syst. Manag..

[27]  Hazel Taylor,et al.  Critical risks in outsourced IT projects: the intractable and the unforeseen , 2006, CACM.

[28]  Ita Richardson,et al.  Guest Editors' Introduction: Why are Small Software Organizations Different? , 2007, IEEE Software.

[29]  Paula Savolainen,et al.  Why do software development projects fail? : emphasising the supplier's perspective and the project start-up , 2011 .

[30]  J. Rodney Turner,et al.  THE HANDBOOK OF PROJECT-BASED MANAGEMENT , 2008 .

[31]  Aileen Cater-Steel,et al.  Process improvement in four small software companies , 2001, Proceedings 2001 Australian Software Engineering Conference.

[32]  York P. Freund.  Critical success factors , 1988 .

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

[34]  Mohamed E. Fayad,et al.  Software Engineering in the Small , 2000 .

[35]  B. Boehm.  Software risk management: principles and practices , 1991, IEEE Software.

[36]  Jarmo J. Ahonen,et al.  Software development project success and failure from the supplier's perspective: A systematic literature review , 2012 .

[37]  Philippe Kruchten,et al.  The Rational Unified Process: An Introduction , 1998 .

[38]  Suzanne Rivard,et al.  An Integrative Contingency Model of Software Project Risk Management , 2001, J. Manag. Inf. Syst..

[39]  Paula Savolainen,et al.  Vague Project Start Makes Project Success of Outsourced Software Development Projects Uncertain , 2010, PROFES.

[40]  Robert L. Glass,et al.  The Standish report: does it really describe a software crisis? , 2006, CACM.

[41]  John M. Smith,et al.  Troubled IT Projects , 2001 .

[42]  H. Taylor,et al.  Congruence between risk management theory and practice in Hong Kong vendor-driven IT projects , 2005 .

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

[44]  Kweku Ewusi-Mensah,et al.  Software Development Failures , 2003 .

[45]  Jarmo J. Ahonen,et al.  Software engineering projects may fail before they are started: Post-mortem analysis of five cancelled projects , 2010, J. Syst. Softw..

[46]  Jae-Nam Lee,et al.  Exploring the Vendor's Process Model in Information Technology Outsourcing , 2008, Commun. Assoc. Inf. Syst..

[47]  A. Boonstra,et al.  Does risk management contribute to IT project success? A meta-analysis of empirical evidence , 2010 .

[48]  K. Artto,et al.  Impact of services on project business , 2008 .

[49]  Karlos Artto,et al.  What is project business , 2005 .

[50]  Torgeir Dingsøyr,et al.  Postmortem: Never Leave a Project without It , 2002, IEEE Softw..

[51]  P. Ghauri,et al.  Project Marketing: Beyond Competitive Bidding , 2002 .

[52]  Hazel Taylor,et al.  Outsourced IT Projects from the Vendor Perspective: Different Goals, Different Risks , 2007, J. Glob. Inf. Manag..

[53]  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.

[54]  J.S. Reel,et al.  Critical Success Factors in Software Projects , 1999, IEEE Softw..

[55]  L BannermanPaul.  Risk and risk management in software projects , 2008 .

[56]  June M. Verner,et al.  In-house software development: what project management practices lead to success? , 2005, IEEE Software.

[57]  H. Tikkanen,et al.  "International Project Marketing: An Introduction to the INPM Approach" , 2003 .

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

[59]  Jeanne W. Ross,et al.  From the Vendor's Perspective: Exploring the Value Proposition in Information Technology Outsourcing 1, 2 , 2003 .

[60]  John M. Smith.  Troubled IT Projects: Prevention and turnaround , 2001 .

[61]  Magne Jørgensen,et al.  Impact of effort estimates on software project work , 2001, Inf. Softw. Technol..

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

[63]  K. Artto,et al.  Project business as a research field , 2008 .

[64]  Tom DeMarco,et al.  A defined process for project post mortem review , 1996, IEEE Software.

[65]  Michael Wybo,et al.  The IT sales cycle as a source of context in IS implementation theory , 2007, Inf. Manag..

[66]  Magne Jørgensen,et al.  Reasons for software effort estimation error: impact of respondent role, information collection approach, and data analysis method , 2004, IEEE Transactions on Software Engineering.