敏捷開發(Agile Development)為近幾年系統開發的熱門方法之一，有著以人為本、富彈性、快速迭代並反饋的特性，縱使在開發過程中客戶的需求更迭頻繁，在專案架構中的角色分工明確，依需求任務分別完成待辦項目，持續產出確認方向後再調整優化，以提升專案開發效率與成功率。
　　而傳產C公司資訊單位的系統開發因系統使用者特性，大多以傳統瀑布模式開發，確認需求內容與影響範圍後再規劃設計，整體開發週期冗長，雖系統完整性高，但實際使用又與需求規劃的內容有所差異，更甚者要再進行優化調整，進而影響系統交付時程與使用意願。本研究使用Scrum方法進行C公司的職能管理系統開發，以期加速系統開發速度並提供符合實務的職能管理系統。
　　個案研究結果顯示，雖導入Scrum敏捷開發目的在加速開發步調，藉由短週期的迭代交付降低變更的範疇，並藉由提早讓使用者進入開發階段測試以期能開發重要且有用的功能，但因個案公司資訊人員皆為首次使用Scrum，在專案開發期間未能掌握Scrum執行的原則，使用者也未能在每次反饋調整時逐漸收斂需求功能，造成系統需求發散導致專案延遲上線。經由此專案開發的結論，本研究整理並歸納個案公司在首次導入Scrum卻造成延遲上線的問題並提出改善建議，以期能提供後續系統做為導入Scrum的借鏡並加以改善，藉此開發出更貼合使用者需求的系統。

　　In recent years, Agile Development has become one of the popular methods of system development with the characteristics of people-oriented, flexible, fast iteration and feedback. Even if the customer's requirements change frequently during the development process, through agile development, system developers can react quickly and complete tasks in time.
　　In this research, for a traditional industry company C, the information system development has been mostly developed using the traditional waterfall model which easily leads to a lengthy overall development cycle. Even more, adjustments are often required which affect the system delivery schedule and willingness to use.
　　In this paper, the introduction of Scrum method to develop the competency management system of human resources department was discussed. The research results show that because the IT department used Scrum for the first time, the system developers failed to catch the principles of Scrum during project development. And the user requirements also failed to gradually converge during each feedback which caused the divergence of requirements and delayed the project schedule. Based on the above experiences, this research also summarizes the problems and reasons of project delays in this case, and proposes improvement suggestions for the future development using Scrum.

學位論文審定書 i
摘要 ii
Abstract iii
目錄 iv
圖次 vi
表次 vii
第一章 緒論 1
1.1 研究背景與動機 1
1.2 研究目的與範圍 2
1.3 研究步驟 4
1.4 研究內容 5
第二章 文獻探討 6
2.1敏捷方法開發之相關理論 6
2.1.1 敏捷開發的緣起 6
2.1.2 敏捷開發Scrum的方法與流程 12
2.2職能管理系統之相關研究 15
2.2.1 職能的定義 15
2.2.2 職能管理與敏捷思維 16
第三章 個案公司現況分析 18
3.1 個案公司背景說明 18
3.2 可行性分析階段 20
3.2 系統分析階段 21
3.3 系統設計階段 21
3.4 程式編碼與測試階段 22
3.5 系統運作與維護階段 23
3.6 系統開發的問題與期望 23
3.7 現況問題分析總結 29
第四章 實施敏捷開發方法之流程探討 34
4.1 系統開發重點整理 34
4.2 Scrum開發流程架構設計 37
4.3 Scrum開發流程導入流程 43
第五章 實證結果分析 45
5.1 改變固化開發思維，導入敏捷觀念並實作 45
5.2 個案公司敏捷方法實際導入結果 46
5.3 導入結論 50
第六章 結論與建議 52
6.1 結論與建議 52
6.2 研究限制與後續研究建議 57
參考文獻 60

一、中文文獻
[1] 張博堯 (2002)，建構績效導向的職能發展體系：知識經濟時代公職人才的培育藍圖，二十一世紀文官體制發展國際會議。
[2] 嚴祥鸞 (1996)，〈參與觀察法〉。頁195-221，收錄於胡幼慧編，《質性研究：理論、方法與本土女性研究實例》，台北市：巨流。
[3] Pichler, Roman. (2010)，SCRUM 敏捷產品管理，博碩文化出版社譯。

二、英文文獻
[1] Anderson, D. J. (2003), “Agile Management for Software Engineering: Applying the Theory of Constraints for Business Results”.
[2] Anthony, S. D. & Johnson, M. W. & Sinfield, J. V. & Altman, E. J. (2008), The Innovator’s Guide to Growth: Putting Disruptive Innovation to Work, New York: Perseus Distribution Services.
[3] Bourque, P. & Fairley, R. E. (eds) (2014), “Guide to the Software Engineering Body of Knowledge”, Version 3.0, IEEE Computer Society; Available at http://www.swebok.org.
[4] Boyatzis, R. E. (1982). The competent manager: a model for effective performance. New York: John Wiley & Sons.
[5] Brooks, Frederick. (1975), “The Mythical Man-Month: Essays on Software Engineering”.
[6] Fortune, Joyce. & White, Diana. (2006), “Framing of Project Critical Success Factors by a Systems Model”, International Journal of Project Management 24(1), 53-65.
[7] Jones, C. (2008), “Applied Software Measurement, McGraw-Hill Education”.
[8] Lofland, J. & Lofland, L. (1984), “Analyzing social settings: A guide to qualitative observation and analysis”, Belmont, C.A.: Wadsworth.
[9] Lyle, M. Spencer. & Signe, M. Spencer. (1993), “Competence at Work: Models for Superior. Performance”, New York, NY: John Wiley and Sons. Inc.
[10] Maxwell, K. D. & Kusters, R. J. (2000), “Software Project Control and Metrics, Information and Software Technology”, Vol. 42, pp. 963-964.
[11] Phan, Dien D. & Vogel, Douglas R. & Nunamaker, Jay F. (1995), “Empirical studies in software development projects: Field survey and OS/400 study”, Information and Management, Volume 28, Issue 4, April 1995, Pages 271-280.
[12] Schwaber, Ken. (1995), “Scrum Development Process”, OOPSLA Business Object Design and Implementation Workshop.
[13] Sims, Chris. & Johnson, Hillary Louise. (2011)，”The Elements of Scrum”，Dymaxicon.

三、網頁部份
[1] Manifesto, A. (2001). https://www.agilealliance.org/.
[2] Schwaber, Ken. & Sutherland, Jeff. (2017), “The Scrum Guide”(Scrum指南), scrumguides.org. https://scrumguides.org/docs/scrumguide/v2017/2017-Scrum-Guide-Chinese-Traditional.pdf
[3] VersionOne (2020), 14th Annual State of Agile Report. https://explore.digital.ai/state-of-agile/14th-annual-state-of-agile-report
[4] Wiki (2021) 職能 https://wiki.mbalib.com/zh-tw/%E8%81%8C%E8%83%BD