軟體維護對於銀行金融資訊領域來說尤為重要，因銀行資訊系統使用的客戶眾多且須符合金管單位的法令規範及消費者權益，在決策過程中往往會以系統穩定性、符合金融法規、資訊安全為主要考量。然而近年來金融科技FinTech為金融領域帶來重大衝擊，從技術、觀念、流程乃至人才招募，各層面都有著顯著的影響。有鑑於快速回應市場（Time to market）的行銷方式儼然成為銀行行銷單位的必須手段，而銀行系統的維護也要跟上這個趨勢。如何在追求穩定又能快速回應變化成為銀行系統維護業務現今的重要課題。本研究嘗試以個案研究方式，透過研究個案維護團隊實際運作敏捷方法的經驗，同時結合ISO/IEC/IEEE 14764維護流程並應用CMMI Institutionalization Design制度化措施建立一套「敏捷式軟體維護流程模式」。本研究的成果或可做為金融資訊單位，在推廣Agile Scrum敏捷方法過程中，當遇到跨業務組織、規劃單位與技術團隊運作時的參考實踐，協助其順利導入敏捷開發與維護流程。

Software maintenance is critical to the stability and sustainability of banking information systems. However, in today’s changing and fast-evolving business environments, time-to-market has become a marketing necessity for banks and thus the maintenance of banking systems needs to keep up with the trend. It is also essential for the banking system maintenance to ensure stability as well as to achieve quick responsiveness to changes. Therefore, this study seeks to examine how the maintenance team in the studied case operates with agility, stability and sustainability, and establishes an agile-based software maintenance process model by combining the ISO/IEC/IEEE 14764 maintenance standard and the CMMI institutionalization design. The research findings can serve as a reference to banking information departments where the Agile method is promoted.

1. 天下雜誌 (2021),成功抵禦疫情衝擊,國泰世華勇奪權威媒體「台灣最佳銀行」的三大關鍵,檢自 https://www.cw.com.tw/article/5118217 (Sep. 30th, 2021)
2. 邱莉婷 (2011),我國金融服務業發展之回顧與展望, 經濟研究第11期(100年4月)
3. 金管會 (2022), 金融監督管理委員會 法規資訊,檢自https://www.fsc.gov.tw/ch/main.jsp?websitelink=fatfooter_list.jsp&contentid=3&mtitle=法規資訊 (May 29th, 2022)
4. 金管會 (2022), 金融監督管理委員會 金融業務統計輯要(111年3月) ,檢自 https://www.banking.gov.tw/ch/home.jsp?id=157&parentpath=0,4&mcustomize=bstatistics_view.jsp&serno=201105120014 (May 23th, 2022)
5. 財金資訊季刊 (2020/05),” 開放銀行趨勢下的 IT 再轉型 - 國泰世華 New Heights 2020 計畫”, 第97期
6. 財資雜誌The Asset (2021), 國泰世華打造數位新金融 國際肯定,檢自 國泰世華打造數位新金融 國際肯定 - C4 富裕人生 - 20210707 - 工商時報 (ctee.com.tw) (Jul. 7th, 2021)
7. 國家教育研究院 (2000),行政院研考會,檢自 http://terms.naer.edu.tw/detail/1309184/ (Mar. 5th, 2022)
8. 陳仲儼, 馬成珉, & 馮立琪. (2010). 應用 ITIL 及 CMMI 來建立並維持資訊服務流程改善. 資訊管理學報, 17(3), 71-105.
9. Abrahamsson, P., Salo, O., Ronkainen, J., & Warsta, J. (2017). Agile software development methods: Review and analysis. arXiv preprint arXiv:1709.08439.
10. Agile Alliance (2001), Manifesto for Agile Software Development, Retrieved from https://agilemanifesto.org/iso/zhcht/manifesto.html (Jun. 1st, 2021)
11. April, A., Abran, A., & Dumke, R. R. (2003). Software maintenance capability maturity model (SM-CMM): process performance measurement. In 13 th International Workshop on Software Measurement–IWSM (pp. 23-25), Montréal, Quebec, Canada.
12. April, A., Huffman Hayes, J., Abran, A., & Dumke, R. (2005). Software Maintenance Maturity Model (SMmm): the software maintenance process model. Journal of Software Maintenance and Evolution: Research and Practice, 17(3), 197-223.
13. Basili, V., Briand, L., Condon, S., Kim, Y. M., Melo, W. L., & Valen, J. D. (1996, March). Understanding and predicting the process of software maintenance releases. In Proceedings of IEEE 18th International Conference on Software Engineering Berlin Germany (pp. 464-474). IEEE.
14. Beck, K., & Andres, C. (2004). Extreme Programming Explained: Embrace Change. Second Edition. XP Ser.
15. Benbasat, I., Goldstein, D. K., & Mead, M. (1987). The case research strategy in studies of information systems. MIS quarterly, 369-386.
16. Bennett, K. H., & Rajlich, V. T. (2000, May). Software maintenance and evolution: a roadmap. In Proceedings of the Conference on the Future of Software Engineering Limerick Ireland (pp. 73-87).
17. Boehm, B. W. (1976). Software engineering. IEEE Trans. Computers, 25(12), 1226-1241.
18. Boehm, B. W. (1983). Seven basic principles of software engineering. Journal of Systems and Software, 3(1), 3-24.
19. Canfora, G., & Cimitile, A. (2001). Software maintenance. In Handbook of Software Engineering and Knowledge Engineering: Volume I: Fundamentals (pp. 91-120).
20. Charette, R. N., Adams, K. M., & White, M. B. (1997). Managing risk in software maintenance. IEEE Software, 14(3), 43-50.
21. Choudhari, J., & Suman, U. (2010, October). Iterative maintenance life cycle using extreme programming. In 2010 International Conference on Advances in Recent Technologies in Communication and Computing NW Washington, DC United States (pp. 401-403). IEEE.
22. CMMI Product Team. (2010). CMMI for Development, Version 1.3 (CMU/SEI-2010-TR-033). Retrieved from the Software Engineering Institute, Carnegie Mellon University website: http://resources.sei.cmu.edu/library/asset-view.cfm?AssetID=9661 (May 7th, 2022)
23. Dave West (2016)，Updates to the Scrum Guide: The 5 Scrum values take center stage, Retrieved from https://www.scrum.org/resources/blog/5-scrum-values-take-center-stage (Feb. 8th, 2022)
24. de Souza, S. C. B., Anquetil, N., & de Oliveira, K. M. (2005, September). A study of the documentation essential to software maintenance. In Proceedings of the 23rd annual international conference on Design of communication: documenting & designing for pervasive information NY, United States (pp. 68-75).
25. de Souza, S. C. B., Anquetil, N., & de Oliveira, K. M. (2006). Which documentation for software maintenance?. Journal of the Brazilian Computer Society, 12(3), 31-44.
26. Dekleva, S. M. (1992). The influence of the information systems development approach on maintenance. MIS quarterly, 355-372.
27. Devulapally, G. K. (2015). Agile in the context of software maintenance: a case study.
28. Gupta, A., & Sharma, S. (2015). Software maintenance: Challenges and issues. Issues, 1(1), 23-25.
29. Hedrick, T. E., Bickman, L., & Rog, D. J. (1993). Applied research design: A practical guide. Sage Publications.
30. Heeager, L. T., & Rose, J. (2015). Optimising agile development practices for the maintenance operation: nine heuristics. Empirical Software Engineering, 20(6), 1762-1784.
31. Ibrahim, K. S. K., Yahaya, J., Mansor, Z., & Deraman, A. (2019, July). The Emergence of agile Maintenance: A preliminary study. In 2019 International Conference on Electrical Engineering and Informatics (ICEEI) Bandung, Indonesia (pp. 146-151). IEEE.
32. ISO/IEC (2006). ISO/IEC 14764 IEEE Std 14764‐2006 International Standard—Software Engineering — Software Life Cycle Processes — Maintenance.
33. ISO/IEC/IEEE. (2022). ISO/IEC/IEEE 14764:2022(E). International Standard - Software engineering — Software life cycle processes — Maintenance (pp. 1–46). IEEE. Retrieved from https://doi.org/10.1109/IEEESTD.2022.9690131(Mar. 20th, 2022)
34. iThome(2020/11/12), 靠技術轉型輔助數位轉型，國泰將技術力變成發展飛輪加速力，檢自 https://www.ithome.com.tw/news/140992 (Jun. 26th, 2021)
35. iThome(2020/12/10), ”國泰世華靠技術驅動全行轉型，打造微服務中臺讓核心瘦身”，檢自 https://www.ithome.com.tw/people/141487 (Jun. 26th, 2021)
36. Jain, P., Sharma, A., & Ahuja, L. (2018). Software Maintainability Estimation in Agile Software Development. International Journal of Open Source Software and Processes (IJOSSP), 9(4), 65-78.
37. Janicic, M. V. Maintenance and maintainability within agile software development . Science of Maintenance. Journal homepage www.m-sci.rs, 1(2021), 1.
38. Kitchenham, B. A., Travassos, G. H., Von Mayrhauser, A., Niessink, F., Schneidewind, N. F., Singer, J., ... & Yang, H. (1999). Towards an ontology of software maintenance. Journal of Software Maintenance: Research and Practice, 11(6), 365-389.
39. Malhotra, R., & Chug, A. (2016, March). Comparative analysis of agile methods and iterative enhancement model in assessment of software maintenance. In 2016 3rd International Conference on Computing for Sustainable Global Development (INDIACom) New Delhi, India (pp. 1271-1276). IEEE.
40. McFeeley, B., & IDEAL, A. (1996). A User's Guide for Software Process Improvement. Software Engineering Institute (SEI).
41. Merriam, S. B. (1988). Case study research in education: A qualitative approach. Jossey-Bass.
42. Miller, G. G. (2001, July). The characteristics of agile software processes. In Technology of Object-Oriented Languages, International Conference on Zurich, Switzerland. (Vol. 1, pp. 0385-0385). IEEE Computer Society.
43. Mohapatra, S. (2009). Software project management. New Delhi, India: Cengage Learning Pvt. Ltd..
44. Mohapatra, S. (2013). Best Practices in Software Maintenance Projects. International Journal of IT/Business Alignment and Governance (IJITBAG), 4(1), 11-26.
45. Niessink, F., & Van Vliet, H. (2000). Software maintenance from a service perspective. Journal of Software Maintenance: Research and Practice, 12(2), 103-120.
46. Omanovic, S., & Buza, E. (2013, October). Importance of stable velocity in agile maintenance. In 2013 XXIV International Conference on Information, Communication and Automation Technologies (ICAT) Sarajevo, Bosnia and Herzegovina (pp. 1-8). IEEE.
47. Pigoski, T. M. (1996). Practical software maintenance: best practices for managing your software investment. Wiley Publishing.
48. Pino, F. J., Ruiz, F., Garcia, F., & Piattini, M. (2012). A software maintenance methodology for small organizations: Agile_MANTEMA. Journal of Software: Evolution and Process, 24(8), 851-876.
49. PMI, (2017). Agile practice guide. Project Management Institute.
50. Poole, C., & Huisman, J. W. (2001). Using extreme programming in a maintenance environment. IEEE Software, 18(6), 42-50.
51. Prochazka, J. (2011). Agile support and Maintenance of IT services. In Information Systems Development (pp. 597-609). Springer, New York, NY.
52. Schneidewind, N. F. (1987). The state of software maintenance. IEEE Transactions on Software Engineering, (3), 303-310.
53. Schwaber, K., & Beedle, M. (2001). Agile software development with Scrum Prentice Hall PTR Upper Saddle River. NJ, USA.
54. Schwaber, K., & Sutherland, J. (2020). “Scrum Guide”. Retrieved from https://scrumguides.org/download.html (Feb. 8th, 2022)
55. Scrum.org (2020), “WHAT IS SCRUM?”, Retrieved from https://www.scrum.org/resources/what-is-scrum (Feb. 8th, 2022)
56. SES Committee. (1998). Ieee standard for software maintenance. IEEE Std, 1219-1998.
57. Shaw, S. (2007). Using agile practices in a maintenance environment. Intelliware Development Inc.
58. Sliger, M., & Broderick, S. (2008). The software project manager's bridge to agility. Addison-wesley professional.
59. Svensson, H., & Host, M. (2005, March). Introducing an agile process in a software maintenance and evolution organization. In Ninth European Conference on Software Maintenance and Reengineering , Manchester, UK (pp. 256-264). IEEE.
60. Syed, K., Barqawi, N., & Mathiassen, L. (2019). Release cycle management: An action research study into a software company. International Journal of Business Information Systems, 30(2), 152-176.
61. Tellis, W. (1997). Introduction to case study. The qualitative report, 269.
62. Tett, G. (2015). The silo effect: The peril of expertise and the promise of breaking down barriers. Simon and Schuster.
63. The Banker (2021). Top 1000 World Banks 2021. Retrieved from https://www.thebanker.com/Top-1000/2021/Top-1000-World-Banks-2021 (May 24th, 2022)
64. Thomas, D. (2006). Agile evolution: Towards the continuous improvement of legacy software. J. Object Technol., 5(7), 19-26.
65. Yin, R. K. (2018). Case study research: Design and methods (6th ed.). Thousand Oaks, CA: Sage.
66. Ziauddin, S. K. T., & Zia, S. (2012). An effort estimation model for agile software development. Advances in computer science and its applications (ACSA), 2(1), 314-324.