INVESTIGATION OF VARIATIONS IN THE SOFTWARE DEVELOPMENT PROCESS: A CASE STUDY

Year 2009, Volume: 9 Issue: 4, 1063 - 1077, 01.11.2009

Yılmaz Gökşen Sabri Erdem Bilgehan Öztürk

Abstract

This study employs the business software project variations in understanding the customer. The relevant literature shows many business software implementation failures and their reasons. Our research is based on a real case study in Turkey and it has a potential for encountering in any location of the world as well as in Turkey. We focus on a business software implementation process and obtain observational data from project meetings and interviews. Our findings show that the most of the factors, that affect the software development process’ success; are understanding the customer, good communication and promises

Keywords

Software development process, software project management, software project failures

References

• Aksoy, E. (2007). “ERP Sistemlerinde Esneklik”, http://www.ias.com.tr/enterprise/articles/20070402-erp-flexibility.html, Nisan , Access Date:June 2009.
• APICS (1999). www.apics.org/magazine/June 99/ERPTravis, Access Date:June 2009.
• Holland C. P. and Light B. (1999). “A Critical Success Factors Model For Enterprise Resource Planning Implementation”, Proceedings of the 7th European Conference on Information, available at: christopherholland.co.uk.
• Jones, C. (2004). “Software Project Management Practices: Failure Versus Success”, CrossTalk: The Journal of Defense Software Engineering, 5-9. available at: www.stsc.hill.af.mil
• Kappelman A. L., Robert M., and Lixuan Z. (2006). “Early Warning Signs of IT Project Failure: The Dominant Dozen”, Information Systems Management, 23:4, 31-36
• Linberg R. K. (1999). “Software developer perceptions about software project failure: a case study”, The Journal of Systems and Software, 49, 177-192.
• Lyytinen, K. & Robey D. (1999). “Learning failure in information systems development”, Information Systems Journal, 9, 85-101.
• Procaccino. D. J, June M. V., Scott P. O. and Marvin E. D. (2002). “Case study: factors for early prediction of software development success”, Information and Software Technology, 44, 53-62.
• Standish Group. (1994). “CHAOS Report”. West Yarmouth, MA: The Standish Group International, Inc.
• Standish Group. (1996). “CHAOS Report”. West Yarmouth, MA: The Standish Group International, Inc.
• Standish Group. (2004). “CHAOS Report”. West Yarmouth, MA: The Standish Group International, Inc.
• Standish Group. (2006). “CHAOS Report”. West Yarmouth, MA: The Standish Group International, Inc.
• Welke, R.W, (1994). “The shifting software development, paradigm”. Data Base, 25 (4), 9-16.