Journal of Information Technology Services (한국IT서비스학회지)

Korea Society of IT Services (한국IT서비스학회)
권호 표지

Exploring on Risk Factors of SI Project Escalation and SI Project De-escalation

SI 프로젝트 범위 증감(Escalation/De-escalation)에 영향을 미치는 위험요소에 대한 연구

  • 김상윤 (한양대학교 대학원 경영학과) ;
  • 백승익 (한양대학교 경영학과) ;
  • 최덕선 (한양대학교 대학원 경영학과) ;
  • 오수진 (쌍용정보통신)
  • Published : 2004.11.30
Download PDF
⟨ Previous Next ⟩

Abstract

For many reasons, SI(Systems Integration) projects can fail. Sometimes, they can result in considerable financial losses to the organizations that undertake them. These projects are abandoned or redirected. However, the cost of project abandonment or redirection can represent a tremendous waste of organizational resources. By managing failure factors carefully, project managers can prevent projects from failing. Types of project failure can be categorized into escalation and de-escalation. Project escalation is that, as projects progress, the project scopes keep increasing. Project de-escalation is that, as projects progress, the project scopes keep decreasing. This study examine relative importance of risk factors that cause project escalation and de-escalation.

Keywords

References

  1. 양경식 & 김현수, ‘국내 소프트웨어 개발 프로젝트의 주요 생산성 요소에 대한 연구’, ‘한국경영정보학회 추계학술대회 논문집’, 1998, pp.311-320
  2. 김현수, ‘국내 SI프로젝트 수행환경 진단 및 위험 관리 방안에 대한 연구’, ‘한국경영과학회지’, 제16권, 제1호, 1999, pp.203-219
  3. Barki, H., Rivard, S. and Talbot, J., 'Towards an Asessment of Software Development Risk,' Journal of MIS, Vol.10, No.2(1993), pp.203-225
  4. Boehm, B.W., 'A Spiral Model for Software Development and Enhancement,' IEEE, Computer, Vol.21, No.5(1988), May, pp.61-72
  5. Boehm, B.W. and DeMarco T., 'Software Risk Management,' IEEE Software, May/June, 1997, pp.17-19
  6. Duncan, W. R., 'A Guide to the Project Management Body of Knowledge,' Project Management Institute, 1996
  7. Higuera, R.P. and Hames, Y.Y., 'Software Risk Management,' CMU/SEII-96-TR-012, Technical Report, June, 1996
  8. Keil, M., 'Turning Around Trobled Software Project : An Exploratory Study of the Deescalation of Commitment to Failing Courses of Action,' MISQ, Vol.15, No.4(1999), Spring, pp.63-88
  9. Keil, M., Cule, P.E., Lyytinen, K. and Schmidt, R.C., 'A Framework for Identifying Software Project Risk,' Communication of the ACM, Vol.41, No.11(1998), pp.76-83 https://doi.org/10.1145/287831.287843
  10. Keil, M., 'Pulling the Plug : Software Project Management and The Proble of Project Escalation,' MISQ, Vol.19, No.4(1995), pp.421-447 https://doi.org/10.2307/249627
  11. Little, R. and Gibson, M., 'Identification of Factors Affecting the Implementation of data warehousing,' Proceedings of the Annual hawaii International Conference on System Sciences, Vol.32(1999), pp.239-
  12. Moynihan, T., 'How Experienced Project Management Assess Risk,' IEEE Software, May/June, 1997, pp.35-41
  13. Ross, J. and Staw, B. M., 'Organizational Escalation and Exit : Lessons from the Shoreham Nuclear Power Plant,' Academy of Management Journal, Vol.36, No.4(1993), pp.701-732 https://doi.org/10.2307/256756