許多研究已證實組織內部資訊系統於建置、導入企業組織過程中，存在許多風險因子。然而在企業組織透過外部廠商建置、取得軟體資訊系統方面，過去研究並未探討跨越多個不同企業組織個體導入資訊系統過程之風險，所以本研究採用個案研究方式，已一實際案例為研究對象，探討企業跨越多個組織個體導入資訊系統過程中的風險因子，及其之間的影響關係。
本研究以Nakatsu & Iacovou於2009年提出的6個風險構面24個風險因子為主，參考其他學者提出的風險構面及風險因子，並與專家討論後，共提出7個風險構面35個風險因子做為本研究基礎架構。使用半結構式訪談法事先擬定好訪談題目，訪談參與專案中任職於不同企業個體組織中不同職位共11位人員，訪談過程中適時的引導受訪者回答，隨後將訪談所收集到的資料採用樣版分析法，重複歸納整理訪談內容後，共發現34個風險因子在研究個案中不同階段出現。並發現其中15個跨組織風險因子，另外依訪談內容繪製出風險因子間的影響關係，最後彙整研究結果並導出風險因子所具備的三種不同特性。
本研究提升對於跨越多個企業組織個體導入資訊系統時風險管理的瞭解。研究結果在實務上可協助企業組織及早偵測、發現相關風險因子；在學術上則提供跨越多個組織個體之風險管理研究上的初步方向，後續研究可更深入了解風險因子的強弱、關係、特性，並採用量化方式加以驗證。

Many studies have addressed the issue of risk in implementing information systems within organization. In addition, it has been verified that risk factors have great effects during the process of implementation. However, few and limited efforts have been entered to understand the managing of risk in cross-organization software implementation project. Therefore, this study attempts to explore the risk factors in cross-organization software implementation project and understand the causal relationship among factors.
To address the objects of the research, this study first reviewed literature and identified seven risk types and thirty five risk factors. The researcher then conducted a case study in a leading automobile manufacturer in Taiwan with an intensive network of suppliers and vendor. A total of 11 semi-structured interviews are performed. Interviewees include participants of this project, from vendor, headquarter of car manufacture, and dealers. After analyzing the collected data, thirty four occurred risk factors are identified in different stages of the project. In addition, among risk factors, fifteen are founded as cross-organization risk factors. Lastly, in addition to specifying three major characteristics of risk, this study also identified causal relationships among found risk factors.
The findings provide organizations an in-depth understanding on risk detection and risk prevention while cross-organization software development. Moreover, future studies are encouraged to conduct quantitative-based empirical studies to verify the identified characteristics of risks and relationships among risk factors.

論文審定書 i
致謝 ii
中文摘要 iii
Abstract iv
第一章 緒論 1
1.1 研究背景 1
1.2 研究動機 2
1.3 研究目的 2
1.4 研究流程 3
1.5 預期研究成果 4
第二章 文獻探討 5
2.1 風險 5
2.2 專案 6
2.3 專案管理 7
2.4 軟體專案風險 8
2.5 風險管理 18
第三章 研究方法 20
3.1 個案研究法 20
3.2 訪談法 21
3.3 樣板分析法 22
3.4 研究嚴謹度 23
3.5 研究限制 24
3.6 個案詳述 24
第四章 個案分析 47
4.1 研究發現 47
4.2 綜合分析 50
4.3 風險因子 62
4.4 風險因子影響關係 72
4.5 跨組織風險因子 95
第五章 結論與建議 103
5.1 研究結論 103
5.2 研究限制 106
5.3 建議 106
參考文獻 110
附錄一：受訪者訪談逐字稿 115
附錄二：預期及未預期風險對策詳細記錄表 154

中文部分
1. 2008政府機關「資訊系統委外開發」概況調查報告。行政院主計處。
2. Patton, M. Q. (1999)。質的評鑑與研究(吳芝儀、李奉儒譯)。台北：桂冠圖書公司。(原著1995年出版)
3. Yin, R. K. (2001)。個案研究法(尚容安譯)。台北：弘智文化事業。
4. 林東清(2010)。資訊管理－e化企業的核心競爭能力。台北：智勝文化。
5. 林東清、劉勇志、楊怡娟、陳秀如(2006)。跨組織知識分享模式之研究－以資訊專案委外為例。資訊管理學報。第55-88頁。
6. 林金定、嚴嘉楓、陳美花(2005)。質性研究方法：訪談模式與實施步驟分析。身心障礙研究。
7. 林明通(2003)。ERP專案風險評估之研究。國立中正大學資訊管理學系碩士論文。
8. 邱雲萍(2004)。資訊系統導入之專案管理－以整合模式架構分析。中山大學管理學院高階經營碩士論文。
9. 陳玉波(2003)。企業專案管理之風險評估流程。國立中山大學資訊管理學系碩士論文。
10. 陳顥文(2010)。以專案管理進行協同產品開發之關鍵成功因素探討-以光通訊產業為例。逢甲大學經營管理碩士論文。
11. 陳李綢（2000）。個案研究。臺北：心理出版社。
12. 管郁君、陳信宏(2007)。從情境觀點探討企業採用跨組織資訊系統之困難－台灣電腦代工廠的個案研究。中山管理評論。第637-666頁。
13. 簡昕潔(2005)。顧客關係管理系統開發專案風險之研究。國立中央大學企業管理研究所碩士論文。
14. 蘇致遠(2011)。以組織訊息處理觀點探討軟體專案風險之降低與對抗。國立中山大學資訊管理學系碩士論文。
15. 王正瑩(2005)。跨國團隊組成、團隊溝通與信任感之研究。國立中山大學人力資源管理研究所碩士論文。
16. 吳百昌(2010)。資訊服務委外風險評估程序之研究－以國軍某單位為例。國防大學管理學院資訊管理學系碩士論文。
17. 許光華、何文榮(1998)。專案管理－理論與實務。台北：華泰書局。
18. 周詳東(2002)。風險管理簡介。中央科學研究院。
19. 宋明哲(1992)。風險為何需要管理－企業的危機應變與風險管理。中華民國管理科學學會。第131-138頁。
20. 楊怡娟(2003)。企業跨組織知識分享之研究－以資訊系統委外為例。國立中山大學資訊管理學系研究所碩士論文。
21. 邱雲萍(2004)。資訊系統導入之專案管理－以整合模式架構分析。國立中山大學管理學院高階經營碩士碩士論文。
22. 林信惠、黃明祥(2002)。軟體專案管理研究架構及趨勢。資訊管理研究。第31-63頁。
23. 陳玉波(2003)。企業專案管理之風險評估流程。國立中山大學資訊管理研究所碩士論文。
英文部分
1. Archibald, R. D. (2003) Managing High-Technology Projrams and Projects. NY, 1976, p19. This book is now in its Third Edition.
2. Addison, T. (2003) “E-commerce project development risks: Evidence from a Delphi survey,” International Journal of Information Management, 23(1), pp. 25-40.
3. Boehm, B. (1991) “Software risk management: Principles and practices,” IEEE Software, 8 (1), pp. 32-41.
4. Barki, H., Rivard, S., Talbot, J. (1993) “Toward an assessment of software development risk,” Journal of Management Information Systems, 10(2), pp. 203-225.
5. Cleland D.I., King W. R. (1983) System Analysis and Project Management. NY：Graw-Hill, Inc.
6. Deephouse, C., Mukhopadhyay, T., Goldenson, D. and Kellner, M. (1996) “Software Processes and Project Performance,” Journal of Management Information Systems, 12(3), pp. 187-205.
7. Ewusi-Mensah K. (1997) “Critical Issues in ABANDONED Information Systems Development Projects,” Communications of the ACM, 40(9), pp. 74-80.
8. Fishburn, P. C. (1984) “Foundations of Risk Measurement: I. Risk as Probable Loss,” Management Science, 30(4), pp. 369-406.
9. Guest, D. E. (1995) ”Human Resource Management and Performance : A Review and Research Agenda,” The International Journal of Human Resource Management. 5: May, pp. 267-299.
10. Han, W.-M. and Huang S.-J (2007) “An empirical analysis of risk components and performance on software projects,” Journal of System and Software, 80(1), pp. 42-50.
11. Hsu, J. S.-C., Chang, J. Y. T., Klein. G. and Jiang, J. J. (2011) “Exploring the impact of team mental models on information utilization and project performance in system development,” International Journal of Project Management, 29(1), pp. 1-12.
12. Jick, T. D. (1979) “Mixing qualitative and quantitative methods: triangulation in action,” Administrative Science Quarterly, 24(4), pp. 602-611.
13. Kitchenham. B., Linkman, S. (1997) “Estimates, uncertainty, and risk,” IEEE Software, 14(3), pp 69-74.
14. Kerzner, Harold. (1990) Project Management a System Approach to Planning, Scheduling and Controlling. NY: Van Nostrand Reinhold.
15. Lowrance, W. (1976) Of Acceptable Risk: Science and the Determination of Safety. Los Altos, CA: William Kaufmann.
16. Lewis, James P. (2003) Project Leadership. McGraw-Hill.
17. McKeen, J. D., Guimaraes, T., Wetherbe, J. C. (1994) “The relationship between user participation and user satisfaction: an investigation of four contingency factors,” MIS Quarterly, 18(4), 427-451.
18. Minichiello V., Aroni R., Timewell E., Alexander L. (1995) In-depth Interviewing, Second Edition. South Melbourne: Longman.
19. Maccoby E., Maccoby N. (1954) “The Interview: A Tool of Social Science. In: G. Lindzey（Ed.）Handbook of Social Psychology,” Massachusetts: Addison-Wesley.
20. Na, K.-S., Li, X., Simpson, J. T. and Kim, K.-Y. (2004) “Uncertainty profile and software proect performance: a cross-national comparison,” The Journal of Systems and Software, 70(1-2), 155-163.
21. Nakatsu, R. T., Iacovou, C. L. (2009) “A comparative study of important risk factors involved in offshore and domestic outsourcing of software development projects: A two-panel Delphi study,” Information & Management, 46(1), 57-68
22. Schwalbe, K., (2009). Information Technology Project Management, 6th ed. Cengage Learning.
23. SEI (1992). The SEI Approach to Managing Software Technical Risks. Bridge, October 1992, pp. 19–21.
24. Surya Lovejoy. (1996) A Systematic Approach to Getting Results. Gower, USA.
25. Sumner, M. (2000) “Risk factors in enterprise-wide/ERP projects,” Journal of Information Technology, 15(4), 317-327.
26. The PMI Standard Committee. (2000) A Guide to the Project Management Body of Knowledge. Project Management Journal.
27. Thomsett, R. (1993) Third wave project management: a handbook for managing the complex information systems for the 1990s. Prentice-Hall, Inc.
28. Wallace, L., Keil, M. and Rai, A. (2004b) “How software project risk affects project performance: an investigation of the dimensions of risk and an exploratory model,” Decision Science, 35(2), pp. 289-321.
29. Webster's Third New International Dictionary. Springfield, Massachusetts: Merriam-Webster, c 1981.
30. Williams, C. A., Heins, R. M. (1989) Risk Management and Insurance, 6th ed., New York：McGraw-Hill Book Co.
31. Xia W. and Lee, G. (2005) “Complexity of information systems development projects: conceptualization and measurement development,” Journal of Management Information System, 22(1), pp. 45-83.
網站資料：
1. 鄭偉萍(2011)。【管理筆記】專案管理軟技巧。鼎新知識學院。2013.06.10取自http://dsa.dsc.com.tw/KM/KMItem.aspx?s=0000000642