創新與速度是企業競爭致勝的關鍵因素，企業組織管理也隨著經營環境的瞬息萬變，面臨艱鉅的挑戰。如何調整組織文化更具彈性，隨機應變並發揮團隊的綜效，儼然成為企業急迫面對的主要課題。
本研究旨在評估個案公司Scrum導入之實踐，先經由文獻探討深入瞭解Scrum的精神價值與原則方法，以個案公司員工為對象，採用問卷調查方式評估個案公司導入Scrum管理方式之實踐程度  ，並透過彙整資料與分析找出員工族群、Scrum管理方式實踐程度與Scrum關鍵成功因素之間的關聯性與差異性。
研究結果顯示：以Scrum關鍵成功因素問卷評估個案公司之導入Scrum後之實踐程度為普通；個案公司不同員工族群與關鍵成功因素的組織、人員與方法技術構面之實踐程度有顯著差異，不同年資族群與關鍵成功因素的人員、流程、方法技術與與專案構面之間有關聯性。另外，透過個案公司員工實踐程度之資料彙整分析，本研究亦指出個案公司實踐程度不佳之關鍵成功因素為：「個人或團隊的激勵制度」、「降低超時工作」與「提供相對應的技術培訓」等關鍵成功因素，並建議個案公司優先改善。最後，期望本研究結果能作為個案公司流程優化或其他準備導入的企業之參考，以減少導入障礙，並加速獲得導入Scrum所帶來的效益。

Innovation and speed are key factors in winning business competitions. Companies are also faced with difficult challenges in their organization and management in the rapidly changing operation environment. How to adjust and have a more flexible organizational culture to improvise and create group synergy has become an important issue that companies are forced to face with.
This study aims to evaluate the practice of Scrum introduced to a case company. First the study has an in-depth understanding of spiritual values and principles and methods of Scrum through literature review, taking employees of the case company as the study object, and using the questionnaire survey to assess the degree of case company's practice of Scrum management to find the correlations and difference between employee groups, degree of practice of Scrum management, and key success factors of Scrum through summarizing and analyzing data.
The results show that: degree of practice of Scrum after introduced to case company is medium evaluated through key success factors   questionnaire of Scrum; different employees groups of case company show significant differences to key success factors in organization, staff, and technical facets; different seniority groups show correlation to key success factors in staff, processes, technical and project facets. In addition, through summarizing and analyzing information on the degree of practice of Scrum for case company's employees, the study also points out that key success factors to low degree of practice of case company are: “individual or team incentive mechanism”, “reducing overtime work”, and “providing corresponding technical training”, and suggests that the company give priority to the improvement of these factors. Finally, results of this study are expected to serve as a reference for case company's process optimization or for other companies who prepare to introduce Scrum, in order to reduce obstacles and facilitate the benefits of introducing Scrum.

主目錄
主目錄 V
表目錄 VII
圖目錄 VIII
第一章 緒論 1
第一節 研究背景 1
第二節 研究動機 2
第三節 研究目的 2
第四節 研究流程 3
第二章 文獻探討 7
第一節 Scrum 7
第二節 關鍵成功因素 12
第三章 研究方法與設計 16
第一節 研究方法 16
第二節 研究架構 16
第三節 問卷設計 19
第四節 研究對象 26
第五節 資料分析方法 26
第四章 研究結果與分析 28
第一節 問卷回收情形 28
第二節 樣本結構分析 28
第三節 信效度分析 31
第四節 ?述性統計 33
第五節 變異數分析 36
第六節 迴歸分析 40
第七節 假設檢定結果 42
第五章 研究討論 45
第一節 研究討論 45
第二節 深入訪談與其他發現 48
第六章 研究結論與建議 62
第一節 研究結論 62
第二節 管理意涵 63
第三節 研究建議與限制 64
參考文獻 66
附錄一 研究問卷 71
附錄二 開放式問卷回饋 83
表目錄
表3-1 問卷操作型定義與參考相關文獻 19
表4-1 統計樣本結構分布概況 28
表4-2 信度分析表 31
表4-3 效度分析表 32
表4-4 敘述性統計分析彙整表 33
表4-5 問卷實踐程度後三名問項 34
表4-6 專案類型與專案成功率彙整表 35
表4-7 ANOVA分析結果彙整表 37
表4-8 事後多重比較結果彙整表 39
表4-9 問卷各構面與認知導入實踐程度迴歸分析結果彙整表 41
表4-10 問卷各構面認知與提高工作效率迴歸分析結果彙整表 41
表4-11假設鑑定結果 42
表5-1 受訪者彙整表 48
表5-2 問卷各構面與認知導入實踐程度迴歸分析結果彙整表 49
表5-3 訪談內容重點彙整表 56
圖目錄
圖1-1 研究流程圖 4
圖2-1 Scrum基本流程 8
圖3-1 研究架構 17

一、 中文部分
1.李茂興譯，Stephen P. Robbins著，1986，管理概論－理論與實務，台北：曉園出版社。
2.邱皓政，2004，社會與行為科學的量化研究與統計分析: SPSS中文視窗版資料分析範例解析(二版)，台北：五南出版社。
3.吳思華，1988，產業政策與企業策略，台北：中國經濟企業研究所。
4.林昌汶，2004，知識型技術服務業關鍵成功因素之研究，大同大學事業經營學系碩士論文。
5.劉振杰，2007，專案績效影響因素之探討，國立台灣科技大學企業管理系EMBA在職專班碩士學位論文。
二、 英文部分
6.Begel, A., & Nagappan, N. (2007). “Usage and perceptions of agile software development in an industrial context: An exploratory study,” Paper presented at the Empirical Software Engineering and Measurement, 2007. ESEM 2007. First International Symposium on, pp. 255-264.
7.Boynton, A. C., & Zmud, R. W. (1984). “An assessment of critical success factors,” Sloan management review, 54(8), pp.17-27.
8.Cadle, J., & Yeates, D. Project management for information systems (5th ed.), Pearson education, New York, 1978.
9.Chow, T., & Cao, D. B. (2008). “A survey study of critical success factors in agile software projects,” Journal of Systems and Software, 81(6), pp.961-971.
10.Keith, C. Agile Game: Development with Scrum, Addison-Wesley, New York, 2010.
11.Cohn, M. Succeeding with Agile: Software Development Using Scrum, Addison-Wesley, New York, 2009.
12.Cooke, T. (2002). “The real success factors on projects,” International journal of project management, 20(3), pp.185-190.
13.Daniel, D. R. (1961). “Management information crisis.” Harvard Business Review, 39(5), pp.111-116.
14.DeSanctis, G. (1983). “Expectancy theory as an explanation of voluntary use of a decision-support system,” Psychological Reports, 52(1), pp.247-260.
15.Dulock, M. J., & Long, H. (2015). Digital collections are a sprint, not a marathon: Adapting scrum project management techniques to library digital initiatives.Information Technology and Libraries, 34(4), 5-17.
16.Dybå, T., & Dingsyr, T. (2008). “Empirical studies of agile software development: A systematic review,” Information and software technology, 50(9), pp.833-859.
17.Fornell, C., & Larcker, D. F. (1981). “Evaluating structural equation models with unobservable variables and measurement error,” Journal of marketing research, pp.39-50.
18.Grunert, K. G., & Ellegaard, C. (1992). “The concept of key success factors: theory and method,” MAPP, pp.22-24.
19.Greene, B. (2004). “Agile methods applied to embedded firmware development,” Paper presented at the Agile Development Conference 2004, pp. 71-77.
20.Koch, A. S. Agile Software Development: Evaluating the Methods for Your Organization, Artech House Inc., London, 2005.
21.Kaiser, H. F. (1970). “A second generation little jiffy,” Psychometrika, 35(4), pp.401-415.
22.Larman, C. Agile and iterative development: a manager's guide, Addison-Wesley, New York, 2004.
23.Leidecker, J. K., & Bruno, A. V. (1984). “Identifying and using critical success factors,” Long range planning, 17(1), pp.23-32.
24.Lee, G., & Xia, W. (2010). “Toward agile: an integrated analysis of quantitative and qualitative field data on software development agility,” Mis Quarterly, 34(1), pp.87-114.
25.Likert, R. (1932). “A technique for the measurement of attitudes,” Archives of Psychology, 140, pp.1-55.
26.Marchenko, A., & Abrahamsson, P. (2008). “Scrum in a multiproject environment: An ethnographically-inspired case study on the adoption challenges,” Paper presented at the Agile, 2008. AGILE '08. Conference, pp. 15-26.
27.Misra, S. C., Kumar, V., & Kumar, U. (2009). “Identifying some important success factors in adopting agile software development practices,” Journal of Systems and Software, 82(11), pp.1869-1890.
28.Nunnally, J. C. Psychometric Theory (2nd ed.), McGraw-Hill, New York,1978.
29.Peterson, D. K., Kim, C., Kim, J. H., & Tamura, T. (2002). “The perceptions of information systems designers from the United States, Japan, and Korea on success and failure factors,” International Journal of Information Management,22(6), pp.421-439.
30.Pinto, J. K., & Slevin, D. P. (1987). “Critical factors in successful project implementation,” Engineering Management, IEEE Transactions on, (1), pp.22-27.
31.Royce, W. W. (1970). “Managing the development of large software systems,” In proceedings of IEEE WESCON, 26(8), pp.1-9.
32.Rockart, J. F. (1978). “Chief executives define their own data needs,” Harvard business review, 57(2), pp.81-93.
33.Schwaber, K., & Sutherland, J. (2014). “The scrum guide,” Scrum Alliance, pp.2.
34.Schwaber, K. (2004). “Agile project management with Scrum,” Microsoft press.
35.Song, X. M., & Parry, M. E. (1996). “What separates Japanese new product winners from losers,” Journal of Product Innovation Management, 13(5), pp.422-439.
36.Sutherland, J., Miller, J., Hollowell, G., Patel, D., & Casanave, C. (1995). “Business Object Design and Implementation,” OOPSLA'95 Workshop Proceedings, pp.118.
37.Sutherland, J. (2001). “Agile can scale: Inventing and reinventing scrum in five companies,” Cutter IT Journal, 14(12), pp.5-11.
38.Sutherland, J. (2004). “Agile development: Lessons learned from the first scrum,” Cutter Agile Project Management Advisory Service: Executive Update, 5(20), pp.1-4.
39.Szalvay, L. (2009). “The State of Scrum,” Agile Journal.
40.Zafar, B., Sattar, A. R., & Mustafa, T. (2010). “Towards Enhancement in the Traditional Processes Upshots by the Implication of Scrum Process,” European Journal of Scientific Research, 40(2), 172-176.