敏捷開發的失敗個案分析－以M公司為例

以作者查詢圖書館館藏

、以作者查詢臺灣博碩士

、以作者查詢全國書目

、勘誤回報

、線上人數：36

、訪客IP：3.147.56.125

姓名

王明怡(Ming-yi Wang) 查詢紙本館藏

畢業系所

資訊管理學系在職專班

論文名稱

敏捷開發的失敗個案分析－以M公司為例
(Agile Programming Failure Case Analysis - Based on M company's project)

相關論文

★ 製藥業的成本會計評估研究─ 一個ABC成本制度的應用	★ 一個保險業的資料採擷應用--業務員的薪酬制度分析
★ 農漁產品電子化交易中分類分級管理之研究	★ 應用類神經網路建構壽險核保決策支援之研究
★ 企業導入ERP之關鍵成功因素-個案研究	★ 體外診斷醫療器材滿足CE及GMP驗證要求之個案研
★ 企業資訊系統委外研究－以個案銀行為例	★ DRAM月平均價格變動分析
★ 定期航運產業運價及運送時間對經營績效影響之研究-以某外商海運公司在台灣經營為例	★ 以交通儲值卡作為電子支付工具的營運模式及可行性分析
★ 軟體公司能力成熟度評估	★ 加速台灣海關的通關便捷化－提升行動化服務的解決方案
★ 以均勻度係數為預測晶圓良率指標之可行性分析-以國內某DRAM廠為例	★ 某公司資訊部門變革失敗之探討
★ 資訊部門導入ITIL 管理機制之現況分析─ 以企業導入ITIL 服務支援為例	★ 導入WCO SAFE 優質企業之可行性分析–以A航空公司為例

檔案

[Endnote RIS 格式]

[Bibtex 格式]

[相關文章]

[文章引用]

[完整記錄]

[館藏目錄]

至系統瀏覽論文 ( 永不開放)

摘要(中)

軟體專案的高失敗率，一直是軟體業的夢魘。為了解決這個棘手的問題，1968年北大西洋公約組織 (NATO) 提出軟體工程的概念，發展至今，已逐漸變成一門學科，軟體開發的成功率卻沒有顯著的提升。軟體工程讓軟體開發變得有組織性、秩序，但是，軟體開發除了規範流程外，還有一些內外部因素，是值得我們探討。
目前描述軟體開發案例的文獻太多是以正面的角度出發，分享成功的經驗，相反的，失敗的分享卻屈指可數，容易造成開發團隊依據「最佳實作 (Best Practices)」進行開發流程，而忽略了要檢視其專案的弱點和降低風險。
本研究個案為一開發客製化軟體的團隊，最後專案以失敗收場。本研究藉由文獻輔以蒐集內部資料和與團隊成員進行訪談，經由分析、歸納後整理出失敗原因並提出相關建議，避免其他團隊再重蹈覆轍。
且研究個案使用的開發方法為，目前在國外大廠被廣泛使用的敏捷方法，但在台灣尚屬萌芽階段，藉由失敗經驗的分享，希望能協助敏捷團隊提高成功率，也希望能對台灣的敏捷開發方法能達到拋磚引玉的效果。

摘要(英)

The high failure rate of software projects has always been a major problem in the industry. In order to resolve this sticky issue, the North Atlantic Treaty Organization (NATO) first raised the term “software engineering” in 1968. Although software engineering has become a popular academic research topic since then, the success rate of software projects has not been dramatically improved. Software engineering is supposed to provide a disciplined and systematic approach to the development of software. Meanwhile, there exist other factors that are worth investigating.
Literatures addressing the success of software development projects are abundant, but very few focus empirically project failure. Consequently, software development teams usually focuses on “Best Practices” without paying attentions to the threats of the project, thus fails to cut down the risks.
This case study looks into a failed software customization project. The project team adopted the Agile methodology for this particular project. Although Agile has been widely employed in the west, it is still in its embryonic stage in Taiwan.
It is a case study based on information collected through internal documents and in depth interviews with project team member. The goal of this study is to gain more practical in sights into the reasons for failure. Recommendations are made to avoid repeating the same pitfalls. We hope this research not only helps agile teams to increase the success rate, but also help to make Agile a popular method in software development.

關鍵字(中)

★ 敏捷開發
★ 軟體開發專案
★ 軟體工程
★ 失敗

關鍵字(英)

★ Agile
★ failure
★ Software Engineering
★ Software Development Projects

論文目次

摘要 i
Abstract ii
誌謝 iii
目錄 iv
圖目錄 vi
表目錄 vii
第一章緒論 1
1.1 緒論 1
1.2 研究動機 2
1.3 研究目的 2
第二章文獻探討 3
2.1 軟體特性 3
2.2 軟體開發模型 5
2.3 瀑布模型 7
2.4 敏捷開發 9
2.5 軟體開發失敗原因探究 17
第三章研究方法 19
3.1 研究方法 19
3.2 研究規劃 19
3.3 研究對象 22
第四章個案分析 24
4.1 個案公司簡介 24
4.2 研究專案簡介 28
4.3 專案應用敏捷開發方法描述 33
第五章研究結果分析 35
5.1 開發團隊不瞭解「敏捷開發方法」 35
5.2 教育訓練不足 37
5.3 錯誤的合約類型 38
5.4 組織文化與敏捷衝突 40
5.5 專案類型與敏捷衝突 43
第六章結論與建議 45
6.1 敏捷態度的培養 45
6.2 敏捷和瀑布的使用時機 48
6.3 恰當的合約類型 50
6.4 組織文化 53
6.5 建議 55
參考文獻 57
附錄一　訪談問題 61
附錄二　逐字稿舉例 62

參考文獻

【英文文獻】
1. Abrahamsson, Pekka & Marchesi, Michele & Maurer, Frank. Agile Processes in Software Engineering and Extreme Programming. NY: Springer-Verlag New York Inc.
2. Abrahamsson, Pekka & Salo, Outi & Ronkainen, Jussi and Warsta, Juhani. (2002). Agile software development methods Review and analysis. Finland: VTT Publications.
3. Arbogast, Tom & Larman,Craig and Vodde, Bas. (2012). Practices for Scaling Lean & Agile Development:Large, Multisite, & Offshore Product Development with Large-Scale Scrum. Boston: Addison-Wesley.
4. Baetjer, Howard Jr. (1998). Software as Capital. IEEE Computer Society Press.
5. Boehm, Barry & Turner, Richard. (2003). Balancing Agility and Discipline: A Guide for the Perplexed. Boston: Addison-Wesley.
6. Jacobson, Ivan. (2002). A Resounding Yes to Agile Processes-But Alson More. The Journal of Information Technology Management. Vol. 15, No 1, pp. 18-24.
7. Kniberg, Henrik. (2007). Scrum and XP from the Trenches. C4Media
8. Smith, Greg & Sidky, Ahmed (2009). Becoming Agile: in an imperfect world. CA: Oreilly & Associates Inc.
9. Shore, James & Warden, Shane. (2007). The Art of Agile Development. CA: O’’Reilly.
10. Schwaber, Ken & Sutherland Jeff. (2011). The Scrum Guide. Scurm.org.
【中文文獻】
1. Beck, Kent. (2002). 極致軟體製程. 李潛瑞譯. 台北市: 台灣培生教育出版股份有限公司.
2. Brooks, Frederick P Jr. (2011). 人月神話：軟體專案管理之道. 錢一一譯. 台北市: 經濟新潮社出版：城邦文化發行.
3. Martin, Robert Cecil. (2005). 敏捷軟體開發:原則、樣式及實務. 林昆穎、吳京子譯. 台北市: 台灣培生教育出版股份有限公司.
4. Pressman, Roger S. (2007). 軟體工程：實踐者的方法. 張晉源譯. 台北市: 美商麥格羅。希爾股份有限公司.
5. Sliger, Michele and Broderick, Stacia. (2009). 軟體專案管理：軟體專案管理者邁向敏捷式橋梁. 何霖譯. 台北市: 碁峰資訊股份有限公司.
6. Sommerville, Ian. (2009). 軟體工程－軟體開發技術與軟體專案管理. 陳玄玲譯. 台北市: 台灣培生教育出版股份有限公司.
7. Yin, Robert K. (2001). 個案研究法. 尚榮安譯. 台北市: 弘智文化.
8. 林佩璇. (2000). 個案研究及其在教育研究上的應用. 載於中正大學教育學研究所主編. 質的教育研究方法. 高雄: 麗文文化.
9. 高添水 (2009). 從承包商角度探討應用系統開發委外產業行銷策略：4C架構觀點. 國立政治大學經營管理碩士學程EMBA學位論文.
10. 黃恆獎、王仕茹、李文瑞. (2007) . 管理學概要. 台北市:華泰文化事業股份有限公司.
11. 劉謦儀. (2003). 國內企業e-Learning實施現況之分析研究. 國立臺灣師範大學工業教育研究所碩士論文.
12. 鄭炳強. (2007). 軟體工程—從實務出發. 台北市: 智勝文化.
13. 顏春煌. (2009). 軟體工程理論與實務. 台北市: 碁峰資訊股份有限公司.
【網頁部份】
1. Agile Alliance, (2002). Manifesto for Agile Software Development. Retrieved May 14, 2012. from http://www.agilemanifesto.org/
2. Bria, Mike. (2008). Createing The Culture For an Agile Enviroment. Retrieved March 16, 2012. from http://www.infoq.com/news/2008/04/smith-creating-agile-environmnt.
3. Charron, Todd. (2011). Organizational Culture and Agile: Does it fit? Retrieved March 16, 2012. from http://www.infoq.com/articles/organizational-culture-and-agile.
4. Flahiff, Joseph. (2011). Integrating Agile into a Waterfall World. Retrieved March 16, 2012. from http://www.infoq.com/articles/agile-in-waterfall-world.
5. Goldsbury, Christopher R. (2011). Known vs Unknown. Retrieved March 14, 2012. from http://www.infoq.com/news/2011/10/Known-vs-Unknown.
6. Goldsbury, Christopher. (2009). Why Agile Adoption Fails in Some Organizations. Retrived March 15, 2012. from http://www.info.com/articles/ failed-agile- adoption-reaso ns/.
7. Hale, Darren. (2009). Build an Agile Team. Retrieved March 14, 2012. from http://www.infoq.com/articles/building-an-agile-team.
8. Hartmann Preuss, Deborah. (2006). Do Agile Practices Make it an Agile Project? Retrieved March 14, 2012. from http://www.infoq.com/ articles/agile-values-and-practic.
9. Hastie, Shane. (2011). Agile Contracts Primer Available for Download Retrieved March 15, 2012. from http://www.infoq.com/news/2011/12/agile-contracts-primer
10. Hazrati, Vikas. (2011). Characteristics of an Agile Organization. RetrievedMarch 16, 2012. from http://www.infoq.com/news/2011/01/characteristics-agile-org
11. Humphrey, Watts S. (2002). Five reasons why software projects fail. Retrieved May 15, 2012. from http://www.computerworld.com/s/article/71209/Why_Projects_Fail
12. Kelly, Alan. (2011). Agile Contracts. Retrieved May 15, 2012 from http://www.infoq /com/articles/agile-contracts.
13. Levine, Ronda. (2011). Why Do Agile Projects Fail? Retrieved May 14, 2012. from http:// www.brighthub.com/office/project-management/articles/55778.aspx.
14. Niebudek, Marcin. (2011). Agile Team Meets a Fixed Price Contract. Retrieved March 15, 2012. from http://www.infoq.com/articles/agile-team-fixed-price-contract.
15. Peplow, Tom. (2008). When should I use agile methods on my software project? Retrieved May 6, 2012. from http://blogs.imeta.co.uk/ TPeplow/archive/2008/11/28/whe n-should- i-use-agile-methods-on-my-software-project.aspx.
16. Philip, Matthew. (2011). Are You a Whole Team? Retrieved March 14, 2012. from http:// www.infoq.com/articles/whole-team.
17. Rees, Dafydd. (2007). Cultivating Agile Attitudes Retrieved March 14, 2012. from http://www.infoq.com/articles/cultivating-agile-attitude.
18. Sahota, Michael. (2011). How to Make Your Culture Work with Agile, Kanban & Software Craftsmanship. Retrieved March 16, 2012. from http://www.methodstandtool. com/archive/agileculture.php.
19. Sharma, Rahul. (2010). Confessions of A New Agile Developer. Retrieved March 16, 2012. from http://www.infoq.com/articles/agile-confessions-sharma.
20. Versionone. (2010). State of Agile Development Survey Results. Retrieved March 16, 2012. from http://www.versionone.com/state_of_agile_development_survey/10/.
21. 何勉. (2011). Scrum框架及其背後的原則 (上)－Scrum框架的虛擬代碼描述 Retrieved May 9, 2012. from http://www.infoq.com/cn/articles/scrum-pseudo-code
22. 崔康 (2010). 敏捷軟件測試的文化挑戰. Retrieved March 16, 2012. from http://www. infoq/cn/ news/2010/12/agile-test-culture.

指導教授

范錚強(C.K. Farn)

審核日期

2012-7-16

推文