The Effects of Scope Management on Process Performance and Output Performance in the Information System Development Project : An Analysis from Project Supplier's Perspective

공급자 관점에서 정보시스템 개발 프로젝트의 범위관리활동이 프로세스성과와 결과물성과에 미치는 영향에 대한 연구

  • Published : 2009.09.30

Abstract

Even though the success of the information system (IS) protect becomes a critical issue to an enterprise and there has been a lot of research about finding critical success factors of IS projects, the scope management for the success of IS protect has received little attention in the literature. The purpose of this research is to investigate the effects of the project scope management activities defined by PMI (Project Management Institute) on the performance of the information system project. The focus of this paper is on the project supplier's point of view. This study shows the priority of the scope management activities during the IS Project. The results show the different results depending on the types of the project clients and the project scale. This research reveals that the scope verification is important for the project supplier from the project process view, and that the scope planning/definition is important for the protect client from the project result view. It also shows different results comparing to the conventional recognition about project success. The research results show that the positive relationships between the project scale and the importance of scope management activities, and between the familiarity of suppliers and clients and the importance of the scope management activities. Through this research, we expect that the importance of the scope management in a project will be considered as an important issue, and that this research will lead to various detailed research about this issue.

Keywords

References

  1. 김동수, 양경식, 김현수, "정보시스템 감리의 충실성이 고객 만족도와 프로젝트 성과에 미치는 영향", "한국IT서비스학회지", 제5권, 제2호(2006), pp.59-78
  2. 김상윤, 백승익, 최덕선, 오수진, "SI 프로젝트 범위 증감(Escalation/De-escalation)에 영향을 미치는 위험요소에 대한 연구", "한국SI학회지", 제3권, 제2호(2004), pp.53-64
  3. 김원섭, "검토회의 진행방법과 프로젝트 수행 성과간 상관관계 분석", 한양대학교 경영대학원 석사논문, 1998
  4. 김은홍, 김화영, "SI프로젝트에 있어서 프로젝트 관리자의 역량과 리더십 유형이 프로젝트 성과와 고객만족에 미치는 영향", "한국경영학회지", (2006), pp.157-179
  5. 김화영, 강소라, "IT 프로젝트 관리자의 리더십 유형별 역량이 프로젝트 성과에 미치는 영향", "한국IT서비스학회지", 제7권, 제2호 (2008), pp.91-111
  6. 배재권, 김진화, 김상열, "PMO 역량에 따른 프로젝트 성과에 관한 연구", "경영정보학연구", 제18권, 제1호(2008), pp.53-77
  7. 서창교, 정은희, "프로젝트 위험과 위험관리가 소프트웨어 개발 프로젝트 성과에 미치는 영향", "경영정보학연구", 제13권, 제2호(2003), pp.199-217
  8. 신호균, 전승호, 김창호, "규칙과 사례기반추론 기법을 이용한 프로젝트 범위관리 모듈개발에 관한 연구," "정보학연구", 제7권, 제3호 (2004), pp.127-138
  9. 오교철, "중소 SI기업의 시장확대 및 성장전략 사례연구 : Captive Business를 주로하는 국내 SI기업을 중심으로", 성균관대학교 대학원 석사논문, 2004
  10. 이상엽, "소프트웨어 프로세스 성숙도가 프로젝트성과에 미치는 영향에 관한 연구", 한국외국어대학교 대학원 석사논문, 2000
  11. 이상훈, 이호근, "지식이전 프로세스가 정보시스템 개발 프로젝트 성과에 미치는 영향에 관한 연구", "지식연구", (2007), pp.97-138
  12. 정규성, 최종화, 임춘성, "공급자 및 수요자 관점의 IT프로젝트 성과평가영역 및 요소에 관한 연구", 대한산업공학회 춘계학술대회 논문집, 2005, pp.413-419
  13. Aladwani, A. M., "An Integrated Performance Model of Information Systems Projects", Journal of Management Information Systems, Vol.19, No.1(2002), pp.185-210
  14. Andres, H. P. and R. W. Zmud, "A Contingency Approach to Software Project Coordination", Journal of Management Information Systems, Vol.18, No.3(2002), pp.41-70 https://doi.org/10.1080/07421222.2002.11045695
  15. Applegate, L. M., F. W. McFarland, and J. L. MCKenney, Corporate Information Systems Management (4th ed.), Boston : Mc-Graw-Hill, 1996
  16. Agarwal, N. and U. Rathod, "Defining Success For Software Projects : An Exploratory Revelation," International Journal of Project Management, Vol.24, No.4(2006), pp.358-370 https://doi.org/10.1016/j.ijproman.2005.11.009
  17. Baccarini, D., "The Logical Framework Method for Defining Project Success", Project Management Journal, Vol.30, No.4(1999), pp.25-32
  18. Barki, H., S. Rivard, and J. Talbot, "Toward an Assessment of Software Development Risk", Journal of Management Information Systems, Vol.10, No.2(1993), pp.203-225 https://doi.org/10.1080/07421222.1993.11518006
  19. Barki, H., S. Rivard, and J. Talbot, "An Integrative Contingency Model of Software Risk Management", Journal of Management Information Systems, Vol.17, No.4(2001), pp.37-69 https://doi.org/10.1080/07421222.2001.11045666
  20. Babu, S., "Scope Creep Management", The PROJECT PERFECT White Paper Collection, 2005
  21. Boynton, A. C., R. W. Zmud, and G. C. Jacobs, "The Influence of IT Management Practice on IT Use in Large Corporations", MIS Quarterly, Vol.18, No.3(1994), pp.299-319 https://doi.org/10.2307/249620
  22. Cooprider, J. G. and J. C. Henderson, "Technology- Process Fit : Perspectives on Achieving Prototyping Effectiveness", Journal of Management Information Systems, Vol.7, No.3(1991), pp.67-88
  23. Dai, C. X. and W. G. Wells, "An exploration of project management office features and their relationship to project performance", International Journal of Project Management, Vol.22, No.7(2004), pp.523-532 https://doi.org/10.1016/j.ijproman.2004.04.001
  24. Deephouse, C., T. Mukopadhyay, D. R. Goldenson, and M. I. Kellner, "Software Process and Project Performance", Journal of Management Information Systems, Vol.12, No.3 (1995), pp.187-205 https://doi.org/10.1080/07421222.1995.11518097
  25. Desouza, K. C. and J. R. Evaristo, "Project management offices : A case of knowledgebased archetypes", International Journal of Information Management, Vol.26, No.5(2006), pp.414-423 https://doi.org/10.1016/j.ijinfomgt.2006.07.002
  26. DOE(Department of Energy), How to Measure Performance : A Handbook of Techniques and Tools, 1995
  27. Edstrom, A., "User Influence and the Success of MIS projects : A Contingency Approach", Human Relations, Vol.30, No.7(1977), pp.589-607 https://doi.org/10.1177/001872677703000702
  28. Fortune, J. and D. White, "Framing of Project Critical Success Factors by a Systems Model", International Journal of Project Management, Vol.24, No.1(2006), pp.53-65 https://doi.org/10.1016/j.ijproman.2005.07.004
  29. Frame, J. D., The New Project Management : Tools for an Age of Rapid Change, Corporate Reengineering, and Other Business Realities, Jossey-Bass, 1994
  30. Gibson, G. E. and Y. R. Wang, "Scope Definition, a Key to Project Success", Proceedings of the 2001 COBRA Conference, Royal Institute of Chartered Surveyors (RICS), Glasgow, Scotland, (2001), pp.293-302
  31. Higuera, R. P. and Y. Y. Hames, "Software Risk Management", CMU/SEII-96-TR-012, Technical Report, 1996
  32. Lederer, A. L. and V. Sethi, "Key Prescriptions for Strategic Information Systems Planning", Journal of Management Information Systems, Vol.13, No.1(1996), pp.35-62 https://doi.org/10.1080/07421222.1996.11518111
  33. Mckeen, J. D. and T. Guimaraes, "Successful Strategies for User Participation in Systems Development", Journal of Management Information Systems, Vol.14, No.2(1997), pp.133-150 https://doi.org/10.1080/07421222.1997.11518168
  34. Moynihan, T., "How Experienced Project Managers Assess Risk", IEEE Software, (1997), pp.35-41
  35. Nidumolu, S. A., "Comparison of the Structural Contingency and Risk-Based Perspectives on Coordination and Software Development Projects", Journal of Management Information Systems, Vol.13, No.2(1996), pp. 77-113 https://doi.org/10.1080/07421222.1996.11518124
  36. Nord, G. D. and J. H. Nord, "Information Systems Project Development : Knowledge and Domain Requirement for the Systems Analyst", Industrial Management and Data Systems, Vol.97, No.1(1997), pp.17-24 https://doi.org/10.1108/02635579710161304
  37. Nystedt, S., "Software Complexity and Project Performance", Department of Informatics School of Economics and Commercial Law at the University of Gothenburg, (1999), pp.95-103
  38. O’Connor, J. and C. Vickroy, "Control of Construction Project Scope", Source Document 6, Austin, TX : Construction Industry Institute, (1986), pp.3-12
  39. Phan, D. D., D. R. Vogel, and J. F. Nunamaker, "Empirical Studies in Software Development Projects : Field Survey and OS/ 400 Study", Information and Management, Vol.28, No.4(1995), pp.271-280 https://doi.org/10.1016/0378-7206(94)00046-L
  40. Pinto, J. K. and D. P. Slevin, "Project Success Definitions and Measurement Techniques", Project Management Journal, Vol.19, No.3(1988), pp.67-73
  41. PMI, Project Management Institute. PMBOK® guide : a guide to project management body of knowledge, World Wide Web : http:// www.pmi.org, 2003
  42. Sarkis, J. and R. P. Sundarraj, "Managing Large-Scale Global ERP Systems : A Case Study at Texas Instruments", Information and Management, Vol.23, No.3(2003), pp. 431-442 https://doi.org/10.1016/S0268-4012(03)00070-7
  43. Schmidt, R., K. Lyytinen, M. Keil, and P. Cule, "Identifying Software Project Risks: An International Delphi Study", Journal of Management Information Systems, Vol.17, No.4(2001), pp.5-36 https://doi.org/10.1080/07421222.2001.11045662
  44. Tait. P. and I. Vessey, 'The Effect of User Involvement on System Success : A Contingency Approach', MIS Quarterly, Vol.12, No.1(1988), pp.91-108 https://doi.org/10.2307/248809
  45. Turner JR. The Handbook of Project-based Management. 2nd ed, England : McGraw-Hill Publishing, 1999
  46. Zhu, Y. and Shu-Ching Chen, "SCOPE : A Conceptual Framework of Ontology-based Program/Project Scope Control", LACCEI International Latin American and Caribbean Conference for Engineering and Technology, 2004