隨著資訊技術的快速發展及廣泛應用，企業對資訊軟硬體的需求日增。軟體在開發時面對的環境越來越多樣化，加以使用者需求不斷變化，若不能有效的導入新的作業流程，將無法有效率的開發及維護系統。本研究以美國卡內基美隆大學軟體工程學院（Software Engineering Institute, SEI) 的IDEAL 模式做敏捷性開發流程導入規畫。本論文透過個案實證的方式，採討企業導入敏捷開發流程的過程與經驗，並分析其實施方案過程中各項問題之解決方式，所建立的流程制度規範，可作為企業在實施敏捷開發後續應用與修改參考。
實證後發現於軟體專案時程方面，Scrum在每個 Sprint 中的所做的持續交付，節省了瀑布式開發流程的前置時間，有助於開發時程的控制。另外，在Scrum中的各Sprint中的增量交付，在開發時程中可以適當回覆使用者需求並加入當前工作，以此滿足使用者需求。最後是軟體品質，在每個 Sprint 中的所做的持續交付，會增加單元及整合測試次數，頻繁的溝通才能使專案進行順利，形成品質就是整個開發團隊責任的觀念。

With the rapid development of information technology and its wide application, the demand for software applications has increased day by day. The environment in which the software is developed is getting more diverse. With the constantly changing needs of users, systems cannot be developed and maintained efficiently without the effective introduction of the new workflow. This study uses the IDEAL model in the Software Engineering Institute (SEI) at Carnegie Mellon University to do agile development process deployment planning. By using case-based approach, the planning process and experience of deploying agile development process to an enterprise, the methods how to solve problems in the implementation of the program, and the established process procedures can be a good reference for those enterprises to deploy and implement the agile software development process.
As empirically found in this case study, the continuous delivery of Scrum in each Sprint can save lead time compared to waterfall development process and help well monitor and control project schedule. In addition, in order to meet the needs of users, the incremental delivery of Sprints in Scrum can properly respond to user needs and accordingly adjust the current work in the development process. Finally, the software quality in the continuous delivery of each Sprint can increase the numbers of unit and integration testing. Frequent communication is needed between developer and users and quality is the responsibility of the entire development team.

一、中文
1、林顯東，2008，「數位物流革命,長春石化集團的 e化、M化及U化」，
台北市：宏典文化。
2、林顯東，2013，「長春石化先導型ERP」，台北市：宏典文化。
3、林顯東，2015，「長春石化社群力App之創新與應用」，
台北市：宏典文化。
4、江謝敏志，2012，「台灣軟體開發專案影響因素與Scrum關係之研究」，
淡江大學資訊管理學系碩士在職專班論文。
5、黃存賢，2013，「資訊系統開發敏捷性與團隊效能權變效果：情緒勞務
之調節探索」，國立東華大學資訊管理碩士學位學程論文。
6、謝禎錕，2016，「運用限制理論探討軟體開發組織進行敏捷轉型之研究-
以某軟體服務公司為例」，國立中央大學資訊管理學系在職專班論文。
7、劉尤媚，2004，「台灣軟板產業概況簡介」,台灣華南金控月刊,P37-42
二、英文
1. Dennis Goldenson & Diane L. Gibson .,2003,「Demonstrating the Impact
and Benefits of CMMI: An Update and Preliminary Results」.
2. E McGuire .,1999,「Software Process imporvement:concepts and
Practices 」.
3. Jiangping Wan,Ruoting Wang .,2010,「Empirical Research on Critical
success Factors of Agile Software Process Improvement」.
4. TsunChow,Dac-BuuCao .,2007,「A survey study of critical success
factors in agile software projects」.
5. 黃世禎.,2017,「Which one is better Plan-Driven or Agile Software
development Processes」.
三、網頁
1. Agile software development,
<https://en.wikipedia.org/wiki/Agile_software_development> ,
2017/11/20
2. Agile Manifesto,<http://www.agilemanifesto.org/.>,2017/11/20
3. Ashley Moran,Why can't developers estimate time,
<http://blog.patchspace.co.uk/why-cant-developers-estimate
-time>, 2017/11/20
4. Chrysler Comprehensive Compensation System ,
<https://en.wikipedia.org/wiki/Chrysler_Comprehensive-
_Compensation-_system> ,2017/11/20

5. DIGITAL TIMES,多層板與軟板的最新製程技術,
<http://www.digitimes.com.tw/tech/dt/n/shwnws.asp?cnlid=1&cat1= 10&cat2=25&id=0000458667_G0F5YBQN7FL1JM6S9OXVA#ixzz4vqLpQHfI>,
2017/11/20
6. iceinto,敏捷开发-Scrum-SCRUM 是一个用于开发和维持复杂产品的框架
<http://www.jianshu.com/p/2c16635a3d93>,2017/11/20
7. Ruddy Lee ,敏捷開發為何會比較快，
<https://ruddyblog.wordpress.com/2016/07/21/敏捷開發為何會比較快
> ,2017/11/20
8. Scrum guide ,
<http://www.scrumguides.org/scrum-guide.html>,2017/11/20
9. Võ Nguyễn Nhật Anh, Agile manifesto and 12 principles behind it
advantages vs disadvantages,
<https://anhvnn.wordpress.com/2016/11/13/agile-manifesto-and-12-
principles-behind-it-advantages-vs-disadvantages/>,2017/11/20
10. McGraw-Hill, 2014, Software Engineering: A Practitioner’s Approach, 8/e
11. Blankenship J., Bussa M., Millett S. ,2011, Managing Agile Projects with Scrum.
In: Pro Agile .NET Development with Scrum.