運用限制理論探討結合瀑布式與敏捷發展的軟體開發—以電商系統為例

以作者查詢圖書館館藏

、以作者查詢臺灣博碩士

、以作者查詢全國書目

、勘誤回報

、線上人數：49

、訪客IP：3.22.41.80

姓名

王湘盈(HSIANG-YING WANG) 查詢紙本館藏

畢業系所

資訊管理學系在職專班

論文名稱

運用限制理論探討結合瀑布式與敏捷發展的軟體開發—以電商系統為例
(Applying Theory of Constraints to the Combined Waterfall and Agile Software Development: A Case Study of E-commerce System Development)

相關論文

★ 專案管理的溝通關鍵路徑探討─以某企業軟體專案為例	★ 運用並探討會議流如何促進敏捷發展過程中團隊溝通與文件化：以T銀行系統開發為例
★ 專案化資訊服務中人力連續派遣決策模式之研究─以高鐵行控資訊設備維護為例	★ 以組織正義觀點介入案件指派決策之研究
★ 應用協調理論建立系統軟體測試中問題改善之協作流程	★ 應用案例式推理於問題管理系統之研究 -以筆記型電腦產品為例
★ 運用限制理論於多專案開發模式的人力資源配置之探討	★ 應用會議流方法於軟體專案開發之個案研究：以翰昇科技公司為例
★ 多重專案、多期再規劃的軟體開發接案決策模式：以南亞科技資訊部門為例	★ 會議導向敏捷軟體開發及系統設計：以大學畢業專題為例
★ 一種基於物件、屬性導向之變更影響分析方法於差異化產品設計	★ 會議流方法對大學畢業專題的團隊合作品質影響之實驗研究
★ 實施敏捷式發展法於大學部畢業專題之行動研究 – 以中央大學資管系為例	★ 建立一個用來評核自然語言需求品質的線上資訊系統
★ 結合本體論與模糊分析網路程序法於軟體測試之風險與風險關聯辨識	★ 在軟體反向工程中針對UML結構模型圖之線上品質評核系統

檔案

[Endnote RIS 格式]

[Bibtex 格式]

[相關文章]

[文章引用]

[完整記錄]

[館藏目錄]

至系統瀏覽論文 (2026-7-1以後開放)

摘要(中)

提供軟體服務的企業為掌握商機，皆在尋求更具適應性和促使專案成功率提高的開發模式。隨著敏捷開發逐漸成為主流，許多文獻發覺傳統瀑布式軟體開發模式仍被大多數企業所採用，同時也發現結合敏捷開發與瀑布式軟體開發模式的混合式軟體開發模式也成為普遍的現況。雖然混合式軟體開發模式可發揮這兩種開發模式的優勢，但仍有其待克服的問題，如：跨開發團隊之間缺乏溝通與合作等情況發生。本研究將以電商產業的資訊部門為例，探索混合式軟體開發模式在實務上發生的問題，並運用限制理論(Theory of Constraints)其邏輯性思維程序(Thinking Process)分析問題間的關聯與問題發生的核心原因，提出可執行的改善行動方案，打破限制並系統性地建構部門間合作的共識。透過研究過程，個案組織得以將限制理論的精神作為後續流程改善的方式，並持續發展混合式軟體開發模式的新協作方式。

摘要(英)

In order to recognize and seize business opportunities, enterprises providing software services are seeking software development models with better adaptation, which can lead to higher success rate in projects. As the Agile methodology has become the mainstream, a substantial literature indicates that the traditional waterfall methodology is still widely adopted by most businesses; meanwhile, the hybrid software development, the combination of the agile methodology and waterfall methodology, is also becoming the norm. Despite the combined advantages of the hybrid software development, there are certain challenges needed to be overcome, such as lack of communication and cooperation between and across development teams. With this context, the purpose of this paper is to explore the practical problems occurred during the process of the hybrid software development, employing the Department of Information Technology in the e-commerce industry as an example. By applying the Thinking Process of the Theory of Constraints and analyzing the association of problems and the main cause logically, the aim is to come up with the feasible plans and hence break the barriers, systematically building the collaboration between departments. Through the process of the research, the case study is able to make good use of the spirit of the Theory of Constraints itself in improving the follow-up process and expand the new collaboration of the hybrid software development.

關鍵字(中)

★ 瀑布式軟體開發
★ 敏捷開發
★ Scrum
★ 限制理論
★ 混合式軟體開發

關鍵字(英)

★ Waterfall methodology
★ Agile methodology
★ Scrum
★ TOC
★ hybrid software development approaches

論文目次

目錄
摘要 i
Abstract ii
目錄 v
圖目錄 vii
表目錄 ix
一、緒論 1
1-1 研究背景 1
1-2 研究動機與問題 2
1-3 研究目的 2
1-4 研究範圍 3
1-5 研究架構 3
二、文獻探討 5
2-1 瀑布式與敏捷軟體開發 5
2-2 混合式軟體開發 9
2-3 限制理論 10
三、研究方法 18
3-1研究問題的定義與範圍 18
3-2 研究方法 18
3-3 研究架構 21
四、個案分析 23
4-1 個案介紹 23
4-2 個案背景 23
4-3 引用限制理論的改善過程 30
五、研究結果 50
5-1 關鍵績效指標 53
5-2 訪談分析 54
5-3 研究效度分析 57
5-4 研究限制與未來發展方向 58
六、結論與未來展望 59
參考文獻 60

參考文獻

參考文獻
1.台灣網路資訊中心（2020），「2020台灣網路報告整體使用現況」，取自https://report.twnic.tw/2020/assets/download/TWNIC_TaiwanInternetReport_2020_CH.pdf（Retrieved on: 2021/06/29）。
2.李榮貴、張盛鴻（2019），TOC 限制理論—從有限走向無限，新北市：中國生產力中心。
3.岸良裕司（2016），問題可以一次解決：跟著管理大師高德拉特的限制理論，學會解決所有工作難題的思考，台北市：時報出版。
4.喬梁（2019），持續交付2.0：實務導向的DevOps，中國：博碩文化股份有限公司。
5.經濟部統計處（2019），「今年電子購物業營收可望再創新猷」，取自：https://www.moea.gov.tw/MNS/populace/news/News.aspx?kind=1&menu_id=40&news_id=86046（Retrieved on: 2021/06/29）。
6.謝禎錕、陳仲儼（2018），「運用限制理論為基礎的敏捷發展轉型歷程模式」，資訊管理學報，25（1），23-53。
7.Alliance, A. (2001). Agile manifesto. Online at http://www.agilemanifesto.org, 6(1).
8.Bhavsar, K., Shah, V., & Gopalan, S. (2020). Scrumbanfall: An Agile Integration of Scrum and Kanban with Waterfall in Software Engineering. International Journal of Innovative Technology and Exploring Engineering (IJITEE), 9(4), 2075-2084.
9.Boehm, B., & Turner, R. (2003). Balancing agility and discipline: A guide for the perplexed. Addison-Wesley Professional.
10.Cao, L., & Li, L. (2015). The impact of cross-channel integration on retailers’ sales growth. Journal of Retailing, 91(2), 198-216.
11.Dettmer, H.W. (1997). Goldratt′s Theory of Constraints: A Systems Approach to Continuous Improvement, ASQC Quality Press, Milwaukee, WI.
12.Dave West, Mike Gilpin, Tom Grant, and Alissa Anderson. (2011). Water- Scrum-Fall Is The Reality Of Agile For Most Organizations Today. Technical Report. Forrester Research Inc.
13.Geras, A., Smith, M., & Miller, J. (2006). Configuring hybrid agile-traditional software processes. In International Conference on Extreme Programming and Agile Processes in Software Engineering, 104-113.
14.Goldratt, E.M. (1990). What Is This Thing Called The Theory of Constraints and How Should It Be Implemented?, The North River Press, Croton-on-Hudson, NY.
15.Goldratt, E. M., & Cox, J. (2016). The goal: a process of ongoing improvement. Routledge.
16.Klein, D. and DeBruine, M. (1995). A thinking process for establishing management policies, Review of Business, 16(3), 31.
17.Kramer, M. (2018). Best practices in systems development lifecycle: An analyses based on the waterfall model. Review of Business & Finance Studies, 9(1), 77-84.
18.Kuhrmann, M., Diebold, P., Münch, J., Tell, P., Garousi, V., Felderer, M., ... & Prause, C. R. (2017). Hybrid software and system development in practice: waterfall, scrum, and beyond. In Proceedings of the 2017 International Conference on Software and System Process, 30-39.
19.Kuhrmann, M., Diebold, P., Munch, J., Tell, P., Trektere, K., McCaffery, F., ... & Prause, C. R. (2018). Hybrid software development approaches in practice: a European perspective. Ieee Software, 36(4), 20-31.
20.Kusters, R. J., van de Leur, Y., Rutten, W. G., & Trienekens, J. J. (2017). When agile meets waterfall-investigating risks and problems on the interface between agile and traditional software development in a hybrid development organization. In International Conference on Enterprise Information Systems, 2, 271-278.
21.Mabin,V. J., Forgeson, S., & Green, L. (2001). Harnessing resistance: using the theory of constraints to assist change management. Journal of Europe an industrial training.
22.McBurney, D. H. (1998). Research methods(4th ed.). Pacific Grove, CA: Brooks/Cole.
23.Neuman, W. L. (2014). Social research methods: Qualitative and quantitative approaches: Pearson new international edition. Pearson Education Limited.
24.Nisar, T. M., & Prabhakar, G. (2017). What factors determine e-satisfaction and consumer spending in e-commerce retailing?. Journal of retailing and consumer services, 39, 135-144.
25.Royce, W. W. (1987). Managing the development of large software systems: concepts and techniques. In Proceedings of the 9th international conference on Software Engineering, 328-338.
26.Schwaber, K., & Sutherland, J. (2012). Software in 30 days: how agile managers beat the odds, delight their customers, and leave competitors in the dust. John Wiley & Sons.
27.Schwaber, K. and Sutherland, J. (2017). Scrum guides (in Chinese), Retrieved from https://www.scrumguides.org/docs/scrumguide/v2017/2017-Scrum-Guide-Chinese-Traditional.pdf (Retrieved on: 2021/06/29)
28.Sidky, A., & Smith, G. (2009). Becoming Agile in an imperfect world. Manning Publications Co., Greenwich CT.
29.Tell, P., Klünder, J., Küpper, S., Raffo, D., MacDonell, S. G., Münch, J., ... & Kuhrmann, M. (2019). What are hybrid development methods made of? an evidence-based characterization. In 2019 IEEE/ACM International Conference on Software and System Processes (ICSSP), 105-114.
30.Theocharis, G., Kuhrmann, M., Münch, J., & Diebold, P. (2015). Is water-scrum-fall reality? on the use of agile and traditional development practices. In International Conference on Product-Focused Software Process Improvement, 149-166.
31.Van Casteren, W. (2017). The Waterfall Model and the Agile Methodologies: A comparison by project characteristics. Research Gate, 1-6.
32.Vijayasarathy, L. R., & Butler, C. W. (2015). Choice of software development methodologies: Do organizational, project, and team characteristics matter?. IEEE software, 33(5), 86-94.
33.Yin, R. K. (1981a). The case study as a serious research strategy. Knowledge, 3(1), 97-114.
34.Yin, R. K. (1981b). The case study crisis: Some answers. Administrative science quarterly, 26(1), 58-65.
35.Yin, R. K. (2014)。質性研究：從開始到完成(Qualitative research from start to finish 2nd Edition)(李政賢譯)。臺北：五南。(原著出版年：2011)
36.Yin, R. K. (2018). Case study research: Design and methods (6th ed.). Thousand Oaks, CA: Sage.

指導教授

陳仲儼

審核日期

2021-7-13

推文