臺灣博碩士論文加值系統

如今資訊系統已成為企業有效管理不可或缺的組成部分。資訊系統實施的一個主要問題是項目能否按計劃在預算範圍內按時完成。在現實生活中，許多資訊系統專案未能在預算範圍內按時完成。這些可歸因於許多內部和外部因素。

雖然過往文獻在專案成敗的研究不少，但在團隊技能的部分著墨不多，相關研究量化也少，本研究以個案研究方式，訪談公司在資訊系統建置專案，了解在專案團隊成員的技能與影響，在專案管理、專案風險中歸納管理、專業、技術三方面的影響。於專案團隊成員技能上的差異，在有限的樣本中尋找其相似性。

最後經個案了解專案成員對專案成敗的影響，以及因專案特性採取那些處理方法。也比較在過往文獻的分析結果是否相似，從中發現新的專案管理細節。在最終的研究結果提供後續在資訊系統專案管理做一個參考。

Nowadays, information systems have become an indispensable component of the effective management of enterprises. A major issue in the implementation of information systems is whether the project can be completed on time, within budget as planned. In real life, many projects have not been completed on time and within budget. These can be attributed to many internal and external factors.
While there have been many studies on the success and failure of projects in the literature, not much has focus on the role of the project team members. This study attempts to look into how skill-set of the project team affects the success and failure of projects. A multiple case approach is adopted, based on participant observation and in depth interviews. The facets of management, professional, and technical skills are included, and project management and project risks are analyzed. A major focus is on the differences in the skill set possess by the project team members.
The impacts of the project members on the success or failure of the project, including the methods adopted, and the characteristics of the projects, are analyzed through these case studies. This study also compares the results of the finding with previous literature.

第一章 緒 論 1
第一節 前言 1
第二節 研究動機 1
第三節 研究目的 1
第四節 研究流程 2
第五節 論文架構 2
第二章 文獻探討 4
第一節 資訊系統建置的成敗 4
第二節 因建置失敗對資訊服務廠商的訴訟風險 4
第三節 資訊技術領導力是資訊系統成敗的主因 6
第四節 政治因素是系統導入成敗的隱藏主因 9
第五節 ERP 導入失敗的原因 9
第六節 系統失敗風險 12
第七節 管理知能的技能 14
第八節 ERP系統建置風險 16
第九節 資訊系統建置過程中專案團隊內外部參與人員的技能與組合 18
第三章 研究設計 20
第一節 研究方法 20
第二節 研究設計 21
第四章 個案研究-SG公司 26
第一節 SG公司背景 26
第二節 SG公司個案內容 26
第三節 SG公司個案構面整理 33
第四節 SG公司個案小結 37
第五章 個案研究-JJ公司 41
第一節 JJ公司背景 41
第二節 JJ公司個案內容 41
第三節 JJ公司個案構面整理 47
第四節 JJ公司個案小結 50
第六章 結論與建議 54
第一節 結論 54
第二節 管理建議 56
第三節 研究限制 58
第四節 後續研究建議 59
參考文獻 60

中文參考文獻
[1] 韓毓璿 (2006)。B2B 電子商務軟體專案之管理領導與政治權力：個案研究，國立中央大學，碩士論文。
[2] 謝廷豪 (2006)。企業導入ERP的動機，關鍵成功暨避免導致失敗因素之探討：以台灣傳統產業為例，修平學報，13，199-218。
[3] 曾渙釗 (2017)。安瑟ERP專文-ERP系統為何失敗？。2019年1月5日，取自https://www.anser.com.tw/785530887003/2017/1/6/erp-erp
[4] 胡幼慧 (1996)。質性研究：理論、方法及本土女性研究實例。高雄：巨流圖書股份有限公司。

英文參考文獻
[1] Aloini, D., Dulmin, R. and Mininno, V. (2007). “Risk management in ERP project introduction: review of the literature,” Information & Management, 44(6), 547-567.
[2] Barki, H., Rivard, S., Talbot, J. (1993). “Toward an Assessment of Software Development Risk,” Journal of Management information Systems, 10(2), 203-225.
[3] Bort, J. (2013). Bridgestone Sues IBM For $600 Million Over Allegedly Defective System That Plunged The Company Into Chaos. Retrieved March 5, 2019, from https://www.businessinsider.com/bridgestone-sues-ibm-for-600m-2013-11
[4] Clemons C. (1998). “Successful Implementation of an Enterprise System: A Case Study,” Americas conference on Information systems (AMCIS), Meeting, December 31, 1998, Baltimore.
[5] Cunningham, M. (1999). “It’s all about the business.” Information, 13(3), 83.
[6] Denzin, N. K. (1978). The research act: A theoretical introduction to sociological methods, New York: McGraw-Hill; Inc., New York.
[7] Eisenhardt, K. M. (1989). “Building theories from case study research,” Academy of Management Review, 14(4), 532-550.
[8] Hoang, H., Rothaermel, F. T. (2005). “The effect of general and partner-specific alliance experience on joint R&D project performance,” Academy of Management Journal, 48, 332-345.
[9] Information professional. Retrieved June 25, 2019, from https://en.wikipedia.org/wiki/Information_professional.
[10] James, G. (1997). “IT fiascoes. . . and how to avoid them,” Datamation, November: 84–88.
[11] Katz, Robert L. (1990). “Business/Enterprise Modeling,” IBM Systems Journal, 29(4), 509-525.
[12] John F. Mancini (2011). The Rise of the Information Professional. Retrieved June 25, 2019, from https://www.aiim.org/pdfdocuments/Rise-of-the-Information-Professional-White-Paper.pdf
[13] Keil, M., Cule, P. E., Lyytinen, K. and Schmidt, R. C. (1998). “A framework for identifying software project risks,” Communications of the ACM, 41(11), 76-83.
[14] Klein, L. (2012). Social Complexity in Project Management. Retrieved March 5, 2019, from http://www.systemic-excellence-group.com/sites/default/files/121023%20Social%20Complexity%20in%20Project%20Management_0.pdf
[15] Korac-Boisvert, K., Kouzmin, A. (1995). “Transcending soft-core IT disasters in public sector organizations,” Information Infrastructure and Policy, 4 (2), 131-161.
[16] Kwak, Y. H. and Stoddard, J. (2004). “Project risk management: lessons learned from software development environment,” Technovation, 24(11), 915-920.
[17] Laudon, Kenneth C. & Laudon, Jane P. (2014). Management Information System:Managing the Digital Firm (13th Edi.). Prentice-Hall.
[18] Lewis, J.P. (2003). Project Leadership. Mcgraw-Hill; Inc., New York.
[19] Lyons, P. (2005). “Enhancing human resources competitiveness using skill charting methods,” Advances in Competitiveness Research, 13(1), 87‐94.
[20] Markus, M. L. (1981). “Implementation Politics: Top Management Support and User Involvement,” Systems, Objectives, Solutions, 1:203-215.
[21] Markus, M. L., & Pfeffer, J. (1983). “Power and the Design and Implementation of Accounting and Control Systems,” Accounting, Organization and Society, 8:205-218.
[22] McGrath, R. G. (1999). “Falling forward: Real options reasoning and entrepreneurial failure,” Academy of Management Review, 24, 13-30.
[23] Mendel, B. (1999). “Overcoming ERP project hurdles,” InfoWorld, 21(29), 87.
[24] Montealegre, R., Keil, M. (2000). “De-escalating information technology projects: Lessons from the Denver international airport,” MIS Quarterly, 24(3), 417-447.
[25] NARS (2010). The demand for and supply of skills in library and information sciences, archival services and records management. Retrieved June 25, 2019, from http://www.national.archives.gov.za/Final%20Report%2015%20March2010.pdf
[26] Riehl, H. (1998). “Managing with Skills,” Ivey Business Quarterly, 62(4), 50-54.
[27] Robson, C. (1993). Real world research: A resource for social scientists and practitioners-researchers. Massachusetts: Blackwell Pushers.
[28] Scott, J. E, Vessey, I. (2002). “Managing risks in enterprise systems implementations,” Communication of the ACM, 45(4), 74-81.
[29] Shepherd, D. A., Patzelt, H., Williams, T. A., Warnecke, D. (2014). “How does project termination impact project team members? Rapid termination, creeping death, and learning from failure,” Journal of Management Studies, 51(4), 513-546.
[30] Shepherd, D. A., Patzelt, H., Wolfe, M. (2011). “Moving forward from project failure: Negative emotions, affective commitment, and learning from the experience,” Academy of Management Journal, 54, 1229-1259.
[31] Sitkin, S. B., and Pablo, A. L. (1992). “Reconceptualizing the Determinants of Risk Behavior,” Academy of Management Review, 17, 9-39.
[32] Smith, P. G. (1999). “Managing Risk as Product Development Schedules Shrink,” Research-Technology Management, 42(5), 25-32.
[33] Spradley, James. P. (1980). Participant Observation. Holt, Rine-hart and Winston.
[34] Strauss & Corbin (1990). Basics of Qualitative Research：Grounded Theory Procedures and Techniques. Newbury Park: Sage Publications, Inc.
[35] Sumner, M. (2000). “Risk factors in enterprise-wide / ERP projects,” Journal of Information Technology, 15, 317-327.
[36] Thomas, M. (2015). Top 6 Skills Necessary For Project Teams. Retrieved March 5, 2019, from https://www.greycampus.com/blog/project-management/top-six-skills-necessary-for-project-teams
[37] Yin, Robert K. (1984). Case Study Research: Design and Methods. Beverly Hill, CA: Sage Publication Inc.