以敏捷方法進行手機軟體開發之個案研究

以作者查詢圖書館館藏

、以作者查詢臺灣博碩士

、以作者查詢全國書目

、勘誤回報

、線上人數：94

、訪客IP：3.16.66.34

姓名

李延興(Yen-Hsing Lee) 查詢紙本館藏

畢業系所

企業管理學系在職專班

論文名稱

以敏捷方法進行手機軟體開發之個案研究
(Applying the Agile Methods for the Software Development of Mobile Phones: A Case Study)

相關論文

★ 企業流程為核心的食品產業運籌體系規劃:低溫物流部份	★ 以企業流程方法規劃整體飛航後勤維修體系之研究
★ 成衣產業導入ERP運籌管理方案之個案研究	★ 光電產業試產基地之生產最佳化模式：以光投影機為例
★ TFT LCD產業獲利因素之探討	★ 科技事業進行合併/讓售之決策過程與成效之個案探討
★ 企業治理、風險及遵循解決方案導入之個案研究-以職責分離資訊系統為例	★ 品質機能展開與多準則決策於設備開發應用
★ ERP導入品質因素對IFRS轉換專案之影響	★ ERP投資金額對服務品質及導入後IT治理目標之分析
★ ERP 導入問題對專案的影響	★ IFRS轉換對員工退休金計畫影響
★ IFRS轉換問題對IFRS效益的影響	★ 電子產業新產品開發參考模式之發展
★ 應用資料科學方法提昇國防裝備可靠度之研究－以防空系統為例	★ 企業資訊方案行銷歷程之探討-以MES為例

檔案

[Endnote RIS 格式]

[Bibtex 格式]

[相關文章]

[文章引用]

[完整記錄]

[館藏目錄]

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

摘要(中)

手機產業從品牌廠到代工廠的競爭都非常激烈，其產業特性具高複雜性與市場變動快速，手機軟體開發不斷的尋求更有效益的管理方法，以達到更高的開發品質，更短的開發時程，以及更快速的市場應變能力，讓客戶以及公司達到利益最大化。相關研究探討中會說明軟體開發方法論中的瀑布式模型以及敏捷式模型，進而說明到產品開發的關卡式流程，再來會介紹到關卡式流程與敏捷式的混合式模型。本研究挑選較為合適的專案進行個案分析，分析中會先說明手機產業特性以及軟體流程，其流程為傳統的瀑布式模型，再來會說明到這次的個案，個案中使用的是敏捷式開發流程，但導入時會和文獻中的有所不同，因為敏捷式模型是無法套用到所有產業和部門的，所以本研究中也會說明到個案是如何套用敏捷式模型。分析成果的部份，本研究會以定量和定性兩個方式進行，首先，針對初級、次級資料做分析，並在開發時間、人力投入、專案管控等數據資料做討論，以確認敏捷式方式是否可以帶來實際的好處；再來會針對個案同仁進行訪談，以確認在個案中的敏捷方式，是否如同數據中的表現，在數據資料以外方面，對組織是否帶來正面或負面的影響；最後，當發現問題因子時，提列出來進行田口分析，並找出流程的最佳組合。雖然敏捷式開發是以軟體開發做基礎的專案管理方法，但面對嵌入式系統類的軟體卻發現了諸多的限制，混合式模型勢必成為類似方案的解決方法，而如何將傳統流程法和敏捷式方式做混合，將其運用找到一個更合適的平衡點，便是每個執行人員所面臨到的難題，所以個案中的經驗便有著研究的價值。

摘要(英)

The competition of the mobile phone industry from brand factories to foundries is very fierce. Its industrial characteristics are highly complex and the market changes rapidly. The purpose of this research is to find more effective mobile phone software development meth-ods to achieve higher development quality, shorter development timeline, and faster market contingency, to maximize the benefits of customers and companies. The case analysis de-scribes the characteristics of the mobile phone industry and the software process. The process is a traditional waterfall model, then explain to this case. The case uses an agile development process. The adopted model is different from literature, due to the agile model cannot be ap-plied to all industries and departments, so this case study shows how the case is applied to the agile model. This research is conducted in two ways. First, analyze the primary and secondary data, and discuss the development time, manpower input, and project management and control to confirm whether the agile method can bring practical benefits. Interviews with individual colleagues to confirm whether the agile approach in the case is like the performance in the data and whether it has a positive or negative impact on the organization in addition to the data. When problem factors are found, Taguchi method is used to find the best combination of processes. Although agile development is a project management method based on software develop¬ment, in the face of embedded system software, it has found many limitations. The hybrid model is bound to be a solution, and it is worth to study on how to use traditional process methods mixing with agile to find a more appropriate balance point is the problem faced
by each executive.

關鍵字(中)

★ 軟體工程
★ 敏捷開發
★ 極限編程
★ 關卡流程法
★ 敏捷混合
★ 手機軟體開發
★ 田口方法

關鍵字(英)

★ Software Engineering
★ Agile
★ Scrum
★ Extreme Programming
★ Stage Gate
★ Agile Stage-Gate Hybrids
★ Phone Software Development
★ Taguchi Methods

論文目次

摘要……………………………………………………………………………… i
Abstract…………………………………………………………………… ii
誌謝……………………………………………………………………………… iii
目錄……………………………………………………………………………… iv
圖目錄………………………………………………………………………… vi
表目錄………………………………………………………………………… viii
第1章緒論………………………………………………………… 1
1.1 研究背景與動機………………………………………… 1
1.2 研究目的………………………………………………………… 2
1.3 研究限制………………………………………………………… 3
第2章相關研究探討…………………………………… 5
2.1 軟體開發方法論………………………………………… 5
2.2 敏捷式方法…………………………………………………… 7
2.3 同步工程………………………………………………………… 13
2.4 關卡流程法…………………………………………………… 15
2.5 關卡流程法與敏捷合併系統……………… 17
第3章研究規劃……………………………………………… 20
3.1 研究方法 ……………………………………………… 20
3.2 研究架構 ……………………………………………… 21
3.3 訪談對象 ……………………………………………… 24
第4章個案分析……………………………………………… 26
4.1 個案產業專案介紹…………………………………… 26
4.2 手機軟體開發介紹與個案說明………… 30
4.3 手機軟體開發流程介紹………………………… 32
4.4 手機軟體開發組織架構介紹……………… 35
第5章研究結果分析…………………………………… 38
5.1 組織架構導入……………………………………………… 38
5.2 流程導入………………………………………………………… 44
5.3 任務管理方式導入…………………………………… 47
5.4 訪談分析………………………………………………………… 51
5.5 田口方法改善流程…………………………………… 54
第6章結論………………………………………………………… 58
參考文獻…………………………………………………………………… 60
附錄一敏捷式開發了解度問題……………… 65
附錄二專案開發問題…………………………………… 66
附錄三衝刺流程改善…………………………………… 67
附錄四人力配置表………………………………………… 68

參考文獻

Abrar, M. F., Khan, M. S., Ali, S., Ali, U., Majeed, M. F., Ali, A., Amin, B., & Rasheed, N. (2019). “Motivators for Large-Scale Agile Adoption from Management Perspective: A Systematic Literature Review”. IEEE Access, 7, 22660-22674.
Alahyari, H., Gorschek, T., & Svensson, R. B. (2019). “An Exploratory Study of Waste in Software Development Organizations Using Agile or Lean Approaches: A Multiple Case Study at 14 Organizations”. Information and Software Technology, 105, 78-94.
Aslam, W., & Ijaz, F. (2018). “A Quantitative Framework for Task Allocation in Distributed Agile Software Development”. IEEE Access, 6, 15380-15390.
Barlow, J. B., Giboney, J., Keith, M. J., Wilson, D., Schuetzler, R. M., Lowry, P. B., & Vance, A. (2011). “Overview and Guidance on Agile Development in Large Organizations”. Communications of the Association for Information Systems, 29(2), 25-44.
Beck, K., & Gamma, E. (2000). Extreme Programming Explained: Embrace Change. Addison-Wesley Professional.
Buggie, F. D. (2002). “Managers at Work: Set the Fuzzy Front End in Concrete”. Research-Technology Management, 45(4), 11-14.
Cai, Z., Liu, H., Huang, Q., & Liang, L. (2019). “Developing Organizational Agility in Product Innovation: the Roles of IT Capability, KM Capability, and Innovative Climate”. R&D Management, 49(4), 421-438.
Campanelli, A. S., Camilo, R. D., & Parreiras, F. S. (2018). “The Impact of Tailoring Criteria on Agile Practices Adoption: A Survey with Novice Agile Practitioners in Brazil”. Journal of Systems and Software, 137, 366-379.
Cao, L., Mohan, K., Xu, P., & Ramesh, B. (2009). “A Framework for Adapting Agile Development Methodologies”. European Journal of Information Systems, 18(4), 332-343.
Ciccullo, F., Pero, M., Caridi, M., Gosling, J., & Purvis, L. (2018). “Integrating the Environmental and Social Sustainability Pillars into the Lean and Agile Supply Chain Management Paradigms: A Literature Review and Future Research Directions”. Journal of Cleaner Production, 172, 2336-2350.
Cohen, D., Lindvall, M., & Costa, P. (2004). “An Introduction to Agile Methods”. Advances in Computers, 62(03), 1-66.
Conforto, E. C., & Amaral, D. C. (2016). “Agile Project Management and Stage-Gate Model a Hybrid Framework for Technology-Based Companies”. Journal of Engineering and Technology Management, 40, 1-14.
Cooper, R. G. (2016). “Agile Stage-Gate Hybrids: The Next Stage for Product Development Blending Agile and Stage-Gate Methods Can Provide Flexibility, Speed, and Improved Communication in New-Product Development”. Research-Technology Management, 59(1), 21-29.
Cooper, R. G. (2009). “How Companies are Reinventing Their Idea-to-Launch Methodologies”. Research-Technology Management, 52(2), 47-57.
Cooper, R. G., & Kleinschmidt, E. J. (1991). “New Product Processes at Leading Industrial Firms”. Industrial Marketing Management, 20(2), 137-147.
Cooper, R. G., & Sommer, A. F. (2016). “Agile Stage-Gate: New Idea-to-Launch Method for Manufactured New Products Is Faster, More Responsive”. Industrial Marketing Management, 59, 167-180.
Dabney, J. B., & Arthur, J. D. (2019). “Applying Standard Independent Verification and Validation Techniques within An Agile Framework: Identifying and Reconciling Incompatibilities”. Systems Engineering, 22(4), 348-360.
De Meyer, A., & Van Hooland, B. (1990). “The Contribution of Manufacturing to Shortening Design Cycle Times”. R&D Management, 20(3), 229-239.
Dönmez, D., & Grote, G. (2018). “Two Sides of the Same Coin–How Agile Software Development Teams Approach Uncertainty as Threats and Opportunities”. Information and Software Technology, 93, 94-111.
Ebert, C., & Salecker, J. (2009). “Guest Editors′ Introduction: Embedded Software Technologies and Trends”. IEEE Software, 26(3), 14-18.
Graves, S. B. (1989). “The Time-Cost Tradeoff in Research and Development: A Review”. Engineering Costs and Production Economics, 16(1), 1-9.
Gassmann, O., & Von Zedtwitz, M. (2003). “Trends and Determinants of Managing Virtual R&D Teams”. R&D Management, 33(3), 243-262.
Gullo D. J. (2016). Real World Agility: Practical Guidance for Agile Practitioners. Addison-Wesley Professional.
Hidalgo, E. S. (2019). “Adapting the Scrum Framework for Agile Project Management in Science: Case Study of A Distributed Research Initiative”. Heliyon, 5(3), 1-5.
Iqbal, T., Huq, F., & Bhutta, M. K. S. (2018). “Agile Manufacturing Relationship Building with TQM, JIT, and Firm Performance: An Exploratory Study in Apparel Export Industry of Pakistan”. International Journal of Production Economics, 203, 24-37.
Johnson, J. (2018). CHAOS Report: Decision Latency Theory: It Is All About the Interval. The Standish Group.
Karlström, D., & Runeson, P. (2005). “Combining Agile Methods with Stage-Gate Project Management”. IEEE Software, 22(3), 43-49.
Kuhrmann, M., Diebold, P., Münch, J., Tell, P., Trektere, K., Mc Caffery, F., Garousi, V., Felderer, M., Linssen, O., Hanser, E., & Prause, C. (2018). “Hybrid Software Development Approaches in Practice: A European Perspective”. IEEE Software, 36(4), 20-31.
Lister, T. R., & DeMarco, T. (1987). Peopleware: Productive Projects and Teams, Dorset House.
Martin R. L., Golsby-Smith T. (2017). “Management Is Much More than A Science”, Harvard Business Review, 95(5), 128-135.
Medeiros, J., Vasconcelos, A., Silva, C., & Goulão, M. (2018). “Quality of Software Requirements Specification in Agile Projects: A Cross-Case Analysis of Six Companies”. Journal of Systems and Software, 142, 171-194.
Misra, S. C., Kumar, V., & Kumar, U. (2009). “Identifying Some Important Success Factors in Adopting Agile Software Development Practices”. Journal of Systems and Software, 82(11), 1869-1890.
Nerur, S., Mahapatra, R., & Mangalaraj, G. (2005). “Challenges of Migrating to Agile Methodologies”. Communications of the ACM, 48(5), 72–78.
Noel, R., Riquelme, F., Mac Lean, R., Merino, E., Cechinel, C., Barcelos, T. S., Villaroel, R., & Munoz, R. (2018). “Exploring Collaborative Writing of User Stories with Multimodal Learning Analytics: A Case Study on A Software Engineering Course”. IEEE Access, 6, 67783-67798.
Rigby D. K., Sutherland J., Noble A. (2018). “Agile at Scale”. Harvard Business Review, 96(3), 88-96.
Rubin K. S. (2016). Essential Scrum: A Practical Guide to the Most Popular Agile Process. Addison-Wesley Professional.
Schmitz, K., Mahapatra, R., & Nerur, S. (2018). “User Engagement in the Era of Hybrid Agile Methodology”. IEEE Software, 36(2), 32-40.
Schuh, G., Anderl, R., Gausemeier, J., Hompe, M. T., & Wahlster, W. (2017). Industrie 4.0 Maturity Index: Managing the Digital Transformation of Companies. Herbert Utz Verlag.
Sommerville I. (2015). Software Engineering 10/e, Pearson Education.
Sommer, A. F., Hedegaard, C., Dukovska-Popovska, I., & Steger-Jensen, K. (2015). “Improved Product Development Performance Through Agile/Stage-Gate Hybrids: The Next-Generation Stage-Gate Process?”. Research-Technology Management, 58(1), 34-45.
Sutherland J. (2015). Scrum: The Art of Doing Twice the Work in Half the Time. Random House.
Takeuchi, H., & Nonaka, I. (1986). “The New New Product Development Game”. Harvard Business Review, 64(1), 137-146.
Ekincioğlu, C., & Boran, S. (2018). “SMED Methodology Based on Fuzzy Taguchi Method”. Journal of Enterprise Information Management, 31(6), 867-878.
Vallon, R., da Silva Estacio, B. J., Prikladnicki, R., & Grechenig, T. (2018). “Systematic Literature Review on Agile Practices in Global Software Development”. Information and Software Technology, 96, 161-180.
Wheelwright, S. C., & Clark, K. B. (1992). Revolutionizing Product Development: Quantum Leaps in Speed, Efficiency, and Quality. Simon and Schuster.
Yin R. K. (2003). Case Study Research: Design and Methods. Sage Publications.

指導教授

呂俊德(Jun-Der Leu)

審核日期

2019-12-20

推文