跳到主要內容

臺灣博碩士論文加值系統

(44.222.104.206) 您好!臺灣時間:2024/05/23 17:41
字體大小: 字級放大   字級縮小   預設字形  
回查詢結果 :::

詳目顯示

我願授權國圖
: 
twitterline
研究生:林澤宇
研究生(外文):Ze-Yu Lin
論文名稱:導入Scrum之軟體專案開發成效探討-以 M 公司為例
論文名稱(外文):The Effectiveness of Scrum for Software Project Development-A Case Study of Company M
指導教授:林冠成林冠成引用關係
指導教授(外文):Kuan-Cheng Lin
口試委員:陳家榛洪啟舜黃一泓
口試日期:2021-06-09
學位類別:碩士
校院名稱:國立中興大學
系所名稱:資訊管理學系所
學門:電算機學門
學類:電算機一般學類
論文種類:學術論文
論文出版年:2021
畢業學年度:109
語文別:中文
論文頁數:86
中文關鍵詞:敏捷開發Scrum專案軟體開發
外文關鍵詞:AgileScrumProject Software Development
相關次數:
  • 被引用被引用:0
  • 點閱點閱:180
  • 評分評分:
  • 下載下載:0
  • 收藏至我的研究室書目清單書目收藏:0
近年因資訊科技快速的演進,傳統的軟體開發方式已無法面對現在的需求,且傳統的開發方式會有生產產品週期過長、無法靈活面對需求變更與最終產品並不一定符合使用者需求等等的相關問題。

而在20世紀初,有一群領域專家針對傳統開發方式所遇到的問題,進行研究與討論,進而發展出更適用於現代產品開發的方式,即為敏捷開發,因其有著重視溝通、開發週期短、回應變化等特性,能大幅提高產品可用性與專案團隊的效率,因此不但被美國政府採用,連同許多世界五百強的知名企業也是採用了敏捷開發,而在軟體開發產業中,更是成為最蔚為盛行的開發方式。

敏捷開發是指一種原則,而不是特定的規則,故敏捷開發中還能視想解決的問題而分類不同的框架與方法,如有專注於實踐的極限編程與敏捷建模;或是有專注於流程管理的Scrum與Kanban看板;還有重視需求規範和開發的特性驅動開發(FDD-Feature Driven Development)。

雖然敏捷開發已經被證實能有效解決企業上所面臨的一些問題,如能縮短產品週期、提高產品有用度、提高客戶滿意度等等,但敏捷開發並不是所有問題的最佳解法,敏捷開發還是會有它的侷限與不足的地方。

本研究將以個案研究法與訪談調查法的方式,針對個案公司進行訪談與資料蒐集,用以產出訪談結果與分析,根據訪談結果可以得出,在個案公司導入Scrum之後,對於專案進度、團隊合作與個人工作上都有著很正向的改變。

依照訪談的結果顯示,成員們認為導入Scrum後對於專案進度帶來最大的幫助,在滿分5分的情況下得到4.5分的高分;其次為跨部門的改善與個人工作的改善,皆得到了4.1分的次高分,最後則是認為同部門的改善,為改善幅度最小的項目,得到3.7分的平均分數,也藉由訪談的結果,分析出帶來改變的原因。

本研究將個案公司的訪談結果以及導入的過程進行統整並針對專案進度、團隊合作與個人工作三個面向進行分析,最後歸納出結論,在未來建議的部分,則依據研究結果針對個案公司與其他公司,條列可能會遇到的問題與解決方案。

最後期望本篇研究內容與結果,可以提供給同為軟體專案開發產業的公司、其他不同產業性質的公司以及同樣為專案管理研究的研究者做為參考依據。
In recent years, due to the rapid evolution of information technology, traditional software development methods have been unable to meet the current needs, and traditional development methods will have too long production product cycles, unable to flexibly face changes in demand, and final products may not necessarily meet user needs And so on related issues.

At the beginning of the 20th century, a group of domain experts conducted research and discussion on the problems encountered in traditional development methods, and then developed a more suitable method for modern product development, that is, agile development, because of its emphasis on communication and development cycles. Shortness, response to changes and other characteristics can greatly improve product availability and the efficiency of the project team. Therefore, not only has it been adopted by the US government, but also many well-known companies in the world’s top 500 have also adopted agile development. In the software development industry, it has become The most popular development method.

Agile development refers to a principle, not a specific rule. Therefore, in agile development, different frameworks and methods can be classified depending on the problem to be solved, such as extreme programming and agile modeling that focus on practice; or Scrum and Kanban Kanban for process management; and FDD-Feature Driven Development, which emphasizes requirement specification and development.

Although agile development has been proven to effectively solve some of the problems faced by enterprises, such as shortening product cycles, improving product usefulness, and improving customer satisfaction, etc., agile development is not the best solution to all problems. Agile development is still There will be its limitations and shortcomings.

This research will use case study method and interview investigation method to conduct interviews and data collection for the case company to produce interview results and analysis. According to the interview results, it can be concluded that after the case company introduces Scrum, the progress and progress of the project will be There are positive changes in teamwork and personal work.

According to the results of the interview, the members believe that the introduction of Scrum will bring the greatest help to the progress of the project, getting a high score of 4.5 with a full score of 5; the second is the improvement of cross-departmental and personal work, both of which are obtained The second highest score of 4.1 points, and finally the improvement in the same department, for the project with the smallest improvement range, an average score of 3.7 points was obtained. The reasons for the changes were also analyzed through the results of the interview.

This research integrates the interview results of the case company and the import process and analyzes the three aspects of project progress, teamwork and individual work, and finally concludes the conclusions. In the future recommendations, the case company and the case company are analyzed based on the research results. Other companies, list possible problems and solutions.

Finally, I hope that the research content and results of this article can be used as a reference for companies in the same software project development industry, other companies in different industries, and researchers who also research on project management.
摘要 i
Abstract ii
目錄 iv
表目次 vi
圖目次 vii
第一章 緒論 1
1.1. 研究背景 1
1.2. 研究動機與目的 2
第二章 文獻探討 4
2.1. 軟體開發方式 4
2.1.1. 瀑布模型 4
2.1.2. 增量模型 6
2.1.3. 螺旋模型 7
2.1.4. 敏捷模型 9
2.2. 敏捷開發 11
2.3. 敏捷框架比較 13
2.3.1. Scrum 13
2.3.2. Kanban 15
2.3.3. Scrum與Kanban比較 16
2.4. SCRUM框架 16
2.4.1. Scrum價值 17
2.4.2. Scrum團隊 19
2.4.3. Scrum活動 20
2.5. 專案管理之應用工具 21
第三章 研究設計與方法 25
3.1. 研究流程與架構 25
3.2. 研究方法 26
3.2.1. 個案研究法 26
3.2.2. 訪談調查法 27
3.2.3. 三角驗證法 28
3.3. 研究範圍與對象 29
3.4. 訪談問題設計與資料蒐集 30
3.4.1. 訪談題目設計 30
3.4.2. 訪談前測 ( 預測試 Pretests ) 32
3.4.3. 資料蒐集與處理 32
第四章 個案分析與結果 33
4.1. 個案公司介紹 33
4.2. 個案公司導入流程 34
4.2.1. 導入評估與過程 34
4.2.2. 風險評估解決方案 35
4.3. 訪談結果與分析 40
4.3.1. 基本資料與Scrum認識 40
4.3.2. 導入Scrum須具備的條件與遇到的問題 44
4.3.3. 導入Scrum帶來多少幫助 46
4.3.4. 導入Scrum帶來什麼樣的幫助 50
4.3.5. 訪談成效與滿意度調查 58
第五章 結論與建議 60
5.1. 研究結論 60
5.2. 未來建議 62
參考文獻 63
附件一 訪談大綱 66
1.陳彥丞. 專案總是「加預算」還做不完?試試Apple、Google都在用的敏捷式工作法. 2018; Available from: https://www.managertoday.com.tw/topic/view/84/post/55800.
2.Beck, K., et al. Manifesto for Agile Software Development. 2001; Available from: https://agilemanifesto.org/iso/en/manifesto.html.
3.Dingsoyr, T., et al., A decade of agile methodologies: Towards explaining agile software development. Journal of Systems and Software, 2012. 85(6): p. 1213-1221.
4.Consultancy.eu. Half of companies applying Agile methodologies & practices. 2020; Available from: https://www.consultancy.eu/news/4153/half-of-companies-applying-agile-methodologies-practices.
5.Balaji, S., M.S.J.I.J.o.I.T. Murugaiyan, and B. Management, Waterfall vs. V-Model vs. Agile: A comparative study on SDLC. 2012. 2(1): p. 26-30.
6.Royce, W.W. Managing the development of large software systems: concepts and techniques. in Proceedings of the 9th international conference on Software Engineering. 1987.
7.Alshamrani, A. and A.J.I.J.o.C.S.I. Bahattab, A comparison between three SDLC models waterfall model, spiral model, and Incremental/Iterative model. 2015. 12(1): p. 106.
8.Boehm, B.W.J.C., A spiral model of software development and enhancement. 1988. 21(5): p. 61-72.
9.MacKay, J. The Ultimate Guide to Implementing Agile Project Management (and Scrum). 2018; Available from: https://plan.io/blog/what-is-agile-project-management/.
10.Varhol, P., To agility and beyond: The history—and legacy—of agile development.
11.Cockburn, A. Declaration of Interdependence. 2005; Available from: https://alistair.cockburn.us/coming-soon/.
12.Iacovelli, A. and C. Souveyet. Framework for Agile Methods Classification. in MoDISE-EUS. 2008. Citeseer.
13.Takeuchi, H. and I.J.H.b.r. Nonaka, The new new product development game. 1986. 64(1): p. 137-146.
14.Degrace, P. and L.H. Stahl, Wicked Problems, Righteous Solutions: A Catalogue of Modern Software. 1990.
15.Schwaber, K., Scrum development process, in Business object design and implementation. 1997, Springer. p. 117-134.
16.Sutherland, J., Business object design and implementation workshop. 1995. 6(4 %J SIGPLAN OOPS Mess.): p. 170–175.
17.wikipedia. Scrum. Available from: https://zh.wikipedia.org/wiki/Scrum.
18.Sutherland, J., K.J.N. Schwaber, Bolts, and O.o.a.A. Process, The scrum papers. 2007.
19.Sutherland, J. and K. Schwaber, Scrum Guide.
20.Schwaber, K., Agile project management with Scrum. 2004: Microsoft press.
21.Gandomani, T.J., et al., The Role of Project Manager in Agile Software Teams: A Systematic Literature Review. Ieee Access, 2020. 8: p. 117109-117121.
22.邱莉燕. LINE新服務主打無縫體驗,真能成為台灣「超級App」. 2020; Available from: https://www.gvm.com.tw/article/73674.
23.Sutikno, T., et al., WhatsApp, viber and telegram: Which is the best for instant messaging? 2016. 6(3).
24.Slack. A better way to communicate. Available from: https://slack.com/intl/en-tw/.
25.Wagenseil, P.J.T.s.G., Zoom security issues: Here's everything that's gone wrong (so far). 2020. 11.
26.Zoom. 在 Zoom,我們想讓每一個人在世界任何地點都可與人建立聯繫。. Available from: https://zoom.us/zh-tw/accessibility.html.
27.陳雅文. 個案研究法 Case Study. 1995; Available from: https://terms.naer.edu.tw/detail/1681584/.
28.Zainal, Z.J.J.k., Case study as a research method. 2007. 5(1).
29.Yin, R.K.J.M.s., Case study research: Design and methods, applied social research. 1994. 5.
30.McCombes, S., How to do a case study. 2020.
31.Denzin, N.K.J.S.m., Triangulation: A case for methodological evaluation and combination. 1978: p. 339-357.
32.林曉雯. 三角校正
Triangulatioon. 2000; Available from: https://terms.naer.edu.tw/detail/1301798/?index=7.
33.Wilson, V.J.E.b.l. and i. practice, Research methods: triangulation. 2014. 9(1): p. 74-75.
34.Hunt, S.D., R.D. Sparkman Jr, and J.B.J.J.o.m.r. Wilcox, The pretest in survey research: Issues and preliminary findings. 1982. 19(2): p. 269-273.
35.Ageling, W.-J. 10 Reasons Why You Are Doomed to Fail With Scrum. 2020; Available from: https://medium.com/serious-scrum/10-reasons-why-you-are-doomed-to-fail-with-scrum-d130953c4e4f.
36.Paasivaara, M., et al., Using scrum in a globally distributed project: a case study. 2008. 13(6): p. 527-544.
電子全文 電子全文(網際網路公開日期:20240721)
連結至畢業學校之論文網頁點我開啟連結
註: 此連結為研究生畢業學校所提供,不一定有電子全文可供下載,若連結有誤,請點選上方之〝勘誤回報〞功能,我們會盡快修正,謝謝!
QRCODE
 
 
 
 
 
                                                                                                                                                                                                                                                                                                                                                                                                               
第一頁 上一頁 下一頁 最後一頁 top
無相關期刊