Open Access Open Access  Restricted Access Subscription or Fee Access

Organizations’ Perspective on Success and Failure of In-House Software Development

Dr. S.N. Geethalakshmi

Abstract


Project success and failure is a question of perception and that the criteria could vary from project to project. A project that has been perceived to be a failure by one stakeholder may be perceived as a success by another. Knowledge and understanding of success and failure factors, as well as how to measure them and the interactions between these factors have great importance for project management effectiveness. The success or failure of Software Project management consists of two components, namely the technical and non-technical components of software development. Non-technical related components of software development process tend to be under managed. Therefore a study was conducted in India among the industries that are into in-house software development, to investigate the influence of the non-technical components of the software development process, on success and failure of software development from the organizations’ perspective (Practitioners’ view). This study reveals that from organizational perspective the level of customer/user involvement, project manager/staff and software process management contribute most to project success and failure.

Keywords


Success, Failure, Software Development Process, In-house.

Full Text:

PDF

References


Andrew, J.N, and Bytheway (1999). “Successful Software Projects and How to Achieve Them”, IEEE Software, 16(3), pp. 15-17.

Belassi, W., and Tukel, O. I. (1996). “A New Framework for Determining Critical Success/Failure Factors In Projects.” International Journal of Project Management, 14 (3), pp. 141-151.

Cooke-Davies, T. J. (2002). “The Real Success Factors In Projects.” International Journal of Project Management, 20(3), pp. 185-190.

Delisle, C.L., & Thomas, J.L. (2002). Success: Getting traction in a turbulent business climate. In Proceedings of PMI Research Conference, “Frontiers of Project management research and applications,” pp. 14-17, Seattle, WA.

Geethalakshmi, S.N., Shanmugam, A. (2007a). “Success Factors of Software Projects”, First International Conference on Knowledge Management for Productivity and Competitiveness, National Productivity Council, India

Geethalakshmi, S.N. & Shanmugam, A. & Subbarayan, V. (2007b). “Critical Success and Failure Factors of Software Projects”, The International Journal of Technology, Knowledge & Society, 3(1) pp. 103-106.

Irja Hyvari, (2006). “Success of Projects in Difference Organizational Conditions”. Project Management Journal, 37(4), pp. 31-40.

Jurison, J. (1999). “Software Project Management: The Manager's View”, Communications of the Association for Information Systems, Volume 2(17), pp. 1-57.

Lawsche, C. H. (1975), “A Quantitative approach to content validity”, Personnel Psychology, 28(4), pp. 563-575.

Nolan, A.J. (1999). “Learning from Success”, IEEE Software, 16(1), pp. 97-105.

Procaccino, J D. (2002b) “Quantitative Models for Early Prediction of Software Development Success: A Practitioner’s Perspective”. (http://hdl.handle.net/1860/76).

Procaccino, J Drew and June Verner, (2002a). ”Software Practitioner’s Perception of Project Success: A Pilot study, International Journal of Computers, The Internet & Management, 10(1), pp. 20-30

Ray, T. & Eden, C. (2002). On Project Success and Failure in Major Engineering Projects. EURAM 2002.

Reel, J.S., (1999). “Critical Success Factors In Software projects”, IEEE Software, 16(3), pp. 18-23.

Sheila Wilson, (1998). “Failed IT Projects (The Human Factor)”, University of Maryland Bowie State University. http://faculty.ed.umuc.edu/~meinkej/inss690/wilson.htm.

Shenhar, A.J (2001). “One Size does not fit all projects: Exploring Classical Contingency Domains,” Management Science, 47(3), pp. 394-414.

Verner, J.M. and Evanco W.M. (2005). In-House Software Development: What Project Management Practices Lead to Success? IEEE Software, 22(1), pp. 86-92.


Refbacks

  • There are currently no refbacks.


Creative Commons License
This work is licensed under a Creative Commons Attribution 3.0 License.