運用並探討會議流如何促進敏捷發展過程中團隊溝通與文件化：以T銀行系統開發為例

以作者查詢圖書館館藏

、以作者查詢臺灣博碩士

、以作者查詢全國書目

、勘誤回報

、線上人數：27

、訪客IP：18.119.107.96

姓名

蔡宜橙(Yi-Cheng Tsai) 查詢紙本館藏

畢業系所

資訊管理學系在職專班

論文名稱

運用並探討會議流如何促進敏捷發展過程中團隊溝通與文件化：以T銀行系統開發為例

相關論文

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

檔案

[Endnote RIS 格式]

[Bibtex 格式]

[相關文章]

[文章引用]

[完整記錄]

[館藏目錄]

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

摘要(中)

近年來，便利的金融服務轉變成生活的必需品，而行動服務更需要快速且主動的做即時應變，數位化金融環境3.0（Bank 3.0）因此誕生。為了因應瞬息萬變的金融環境，敏捷軟體開發方法成了專案開發的新選擇。敏捷軟體開發方法強調面對面的溝通是很重要的，如何建立專案整體的溝通脈絡，以提升溝通的效率，本研究運用了學者所提出的會議流方法（Meeting-Flow Approach；MFA），來解決專案團隊與協作人員之間的溝通問題。此外，敏捷軟體開發所帶來的另一個文件化的問題，也藉由會議流方法，建立一套適用於敏捷軟體開發方法的文件回饋機制，來達到企業的資訊安全規範。
本研究採用個案研究的方式，探討在敏捷軟體開發方法下導入會議流，及配合Scrum方法的各項會議下，塑模出會議的時序流及資訊流，並進一步分析此方法對於個案成效的幫助。具體而言，本研究除了探討個案所面臨之問題是否獲得改善外，亦藉由關鍵績效指標來衡量會議流的導入是否提升溝通品質，並降低溝通佔整體工作時間的百分比，以及工作的效能是否提升。此外，針對企業所規範的資訊安全文件，是否在會議流導入後，能夠提升文件產出的品質及降低稽核缺失的次數。並針對本研究之導入，與專案成員進行個別訪談，整理及歸納出會議流導入之結論及建議。

摘要(英)

The fast advancement of modern financial technologies (Fintech) has greatly enhanced people’s life. In particular, the mobilization of Fintech aims in providing agile and proactive services, and thus Bank 3.0 has come to serve this need. In order to respond to the dynamic banking environments, the agile approach of service development seems to be useful in this regard. Agile development approach emphasizes communication and less documentation; yet such emphases may lead to undue group communication and lack of documental support. Therefore, this study applies the meetings-flow approach (MFA) to establish a meeting-oriented group process with document feedback loop to support the agile-based service development.
To implement the proposed work, this study adopts the case research methodology. This study reports on a mega banking service project that adopts SCRUM approach and presents the aforementioned problems encountered during the development, and explores how the MFA helps address the problems. Specifically, by modeling the iterative development into the meetings-oriented process loops, the MFA provides a concrete way of showing how the project stakeholders communicate and collaborate to achieve phase goals while preserve important documentation through the collaborative effort. This study also investigates the benefits of the application bringing to the project, and concludes the work to outline its future research directions.

關鍵字(中)

★ 敏捷軟體開發
★ 團隊溝通
★ 會議流
★ Scrum
★ 文件化

關鍵字(英)

★ Banking service development
★ agile development approach
★ meetings flow
★ group communication
★ documentation

論文目次

摘　　　要 i
Abstract ii
誌　　　謝 iii
目　　　錄 v
圖　目　錄 vii
表　目　錄 viii
第一章緒論 1
1.1. 研究背景 1
1.2. 研究動機及目的 2
1.3. 研究範圍 2
1.4. 論文架構 3
第二章文獻探討 4
2.1. 敏捷軟體開發與方法 4
2.2. Scrum方法介紹 8
2.3. Scrum的限制 10
2.4. 會議流 12
第三章研究方法 15
3.1. 個案研究 15
3.2. 研究設計 16
3.3. 資料蒐集 17
3.4. 研究流程 19
第四章個案研究 20
4.1. 個案研究描述 20
4.1.1. 公司介紹 20
4.1.2. 個案介紹 23
4.1.3. 面臨問題 26
4.2. 會議流設計 28
4.2.1. 塑模會議 28
4.2.2. 組織關聯會議 32
4.3. 產生會議流 33
4.3.1. 循序型的會議流 33
4.3.2. 文件化的作業流程 35
第五章研究結果 37
5.1. 關鍵績效指標 37
5.1.1. 導入前後之描述 37
5.1.2. 關鍵績效指標定義 38
5.1.3. 結果與分析 39
5.2. 訪談與分析 41
5.2.1. 訪談程序 41
5.2.2. 個別訪談與結果 42
5.3. 研究限制 47
第六章結論與建議 49
6.1. 研究結論 49
6.2. 研究建議 50
參考文獻 52

參考文獻

中文部份：
1. 邱憶惠（1999）。個案研究：質化取向。國立高雄師範大學教育系教育研究，七期，頁113-127。
2. 孫一仕，施祖琪，蕭俊傑（2015）。Bank3.0：銀行轉型未來式。財團法人台灣金融研訓院。
英文部份：
1. Abdullah, E. and Abdelsatir, E.-T.B. (2013), Extreme programming applied in a large-scale distributed system, Computing, Electrical and Electronics Engineering (ICCEEE), 2013 International Conference on IEEE, 442-446.
2. Ahmad, G., Soomro, T.R., Brohi, M.N. (2014), Agile Methodologies: Comparative Study and Future Direction, European Academic Research , Vol. I, Issue 11, 3826-3841.
3. Aiken, M., (2002). Multilingual communication in electronic meetings. ACM SIGGROUP Bulletin 23 (1), 18–19.
4. Akhtar, M. J., Ahsan, A., & Sadiq, W. Z. (2010). Scrum adoption, acceptance and implementation (a case study of barriers in Pakistan′s IT industry and mandatory improvements). In Industrial Engineering and Engineering Management (IE&EM), 2010 IEEE 17Th International Conference on IEEE, 458-461.
5. Alonzo, M., Aiken, M., (2004). Flaming in electronic communication. Decision Support Systems 36 (3), 205–213.
6. Alshehri, S. and Benedicenti, L. (2013), Prioritizing CRC cards as a simple design tool in extreme programming, Electrical and Computer Engineering (CCECE), 2013 26th Annual IEEE Canadian Conference on IEEE, 1-4.
7. Barker, A., (2007). How to Manage Meetings. Kogan Page Publishers, London, UK, 147 pp.
8. Beck, K., Beedle, M., Van Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M., ... & Thomas, D. (2001). The agile manifesto.
9. Bessam, A., Kimour, M.T., Melit, A. (2009), Separating Users′ Views in a Development Process for Agile Methods, Dependability of Computer Systems, 2009. DepCos-RELCOMEX ′09. Fourth International Conference on IEEE, 61-68.
10. Bettenburg, N. (2014), Studying the Impact of Developer Communication on the Quality and Evolution of a Software System: A Doctoral Dissertation Retrospective, 2014 IEEE International Conference on Software Maintenance and Evolution, 651 - 656.
11. Bhalerao, S., Puntambekar, D., & Ingle, M. (2009), Generalizing Agile software development life cycle. International Journal on Computer Science and Engineering, 1(3), 222-226.
12. Briggs, R.O., Reinig, B.A., de Vreede, G.J., (2007). Meeting satisfaction for technology-supported groups. Small Group Research 38(3), 3–11.
13. Carvalho, F. and Azevedo, L.G. (2013), Service Agile Development Using XP, Service Oriented System Engineering (SOSE), 2013 IEEE 7th International Symposium on IEEE, 254-259.
14. Chen, C.Y. (2011), Managing projects from a client perspective: the concept of the meetings-flow approach, International Journal of Project Management, 29(6), 671-696.
15. Chen, C.Y., (2009). A meetings flow approach for conducting student final-year projects. Journal of Computing Sciences in Colleges 24 (6), 28–34.
16. Chen, C.Y., Chao, K.H., Chen, P.C., (2007). Collaborative project management: the meeting flow information system for software project development (MfPMIS). In: IEEE International Conference on Industrial Engineering and Engineering Management, Singapore.
17. Chen, C.Y., Chong, P.P. (2011). Software engineering education: A study on conducting collaborative senior project development. Journal of Systems and Software, 84(3), 479-491.
18. Chen, C.Y., Hong, Y.C., Chen, P.C. (2014), Effects of the Meetings-Flow Approach on Quality Teamwork in the Training of Software Capstone Projects, IEEE Transactions on Education, 57(3), 201-208.
19. Chen, C.Y., Teng, K.C. (2011). The design and development of a computerized tool support for conducting senior projects in software engineering education. Computers & Education, 56(3), 802-817.
20. de Vreede, G.J., Davison, R.M., Briggs, R.O., (2003). How a silver bullet may lose its shine. Communications of the ACM 46 (8), 96–101.
21. Dennis, A.R., Garfield, M.J., (2003). The adoption and use of GSS in project teams, toward more participative process and outcomes. MIS Quarterly 27 (2), 289–323.
22. Eloranta, V.-P., Koskimies, K., Mikkonen, T., Vuorinen, J. (2013), 2013 IEEE 20th Asia-Pacific Software Engineering Conference, Volume 1, 503-510.
23. Extreme Programming Organization. (2015, October 21). [Online]. Available: http://www.extremeprogramming.org
24. Gallivan, M., Keil, M., (2003). The user-developer communication process: a critical case study. Information System Journal 13 (1), 37–68.
25. Garcia, A.C.B., Kunz, J., Fischer, M., (2005). Voting on the agenda: the key to social efficient meetings. International Journal of Project Management 23 (1), 17–24.
26. Green, E.P., and Frederick T.S. World atlas of seagrasses (2003). Univ of California Press.
27. Hossain, E., Babar, M. A., & Paik, H. Y. (2009). Using scrum in global software development: a systematic literature review. In Global Software Engineering, 2009. ICGSE 2009. Fourth IEEE International Conference on IEEE, 175-184.
28. Howard-Grenville, J., Golden-Biddle, K., Irwin, J., Mao, J., (2011). Liminality as cultural process for cultural change. Organization Science 22 (2), 522–539.
29. ISO, (2003), ISO 10006：2003 Quality management system-Guidelines for quality management in projects.
30. ISO, (2003), ISO 10006：Quality management systems -Guidelines for quality management in projects, 2nd edition.
31. Kajko-Mattsson, M. (2008). Problems in agile trenches. In Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement, 111-119.
32. Kanwal, F., Junaid, K. and Fahiem, M.A. (2010), A Hybrid Software Architecture Evaluation Method for FDD - An Agile Process Model, Computational Intelligence and Software Engineering (CiSE), 2010 International Conference on IEEE, 1-5.
33. Kautz, K. (2009), Customer and user involvement in agile software development. In Agile Processes in Software Engineering and Extreme Programming. Springer Berlin Heidelberg, 2009. 168-173.
34. Kiwan, H., Morgan, Y.L., Benedicenti, L. (2013), Two mathematical modeling approaches for extreme programming, Electrical and Computer Engineering (CCECE), 2013 26th Annual IEEE Canadian Conference on IEEE, 1-5.
35. Koskela, J. (2003), “Software configuration management in agile methods”, VTT publication 514, ESPOO, 2003, pp I-54.
36. Landaeta, R. E., Viscardi, S., & Tolk, A. (2011). Strategic management of scrum projects: An organizational learning perspective. In Technology Management Conference on IEEE (ITMC), 2011 IEEE International, 651-656.
37. Modi, S. and Abbott, P. (2013), Understanding Collaborative Practices in Distributed Agile Development, 2013 IEEE 8th International Conference on Global Software Engineering Workshops, 74-77.
38. Nuevo, E. D., Piattini, M., & Pino, F. J. (2011). Scrum-based methodology for distributed software development. In Global Software Engineering (ICGSE), 2011 6th IEEE International Conference on IEEE, 66-74.
39. Olsson, H.H., Alahyari, H., Bosch, J.(2012). Climbing the “Stairway to Heaven” -- A Mulitiple-Case Study Exploring Barriers in the Transition from Agile Development towards Continuous Deployment of Software, 2012 38th Euromicro Conference on Software Engineering and Advanced Applications, 392-399.
40. Overhage, S. and Schlauderer, S. (2012), Investigating the Long-Term Acceptance of Agile Methodologies: An Empirical Study of Developer Perceptions in Scrum Projects, System Science (HICSS), 2012 45th Hawaii International Conference on IEEE, 5452-5461.
41. PMI, (2013). A Guide to the Project Management Body of Knowledge(PMBOKR Guide) - Fifth Edition : Project Management Institute.
42. Paasivaara, M. and Lassenius, C. (2011), Scaling Scrum in a Large Distributed Project, Empirical Software Engineering and Measurement (ESEM), 2011 International Symposium on IEEE, 363-367.
43. Paetsch, F., Eberlein, A., Maurer, F. (2003), Requirements engineering and agile software development, Enabling Technologies: Infrastructure for Collaborative Enterprises, 2003. WET ICE 2003. Proceedings. Twelfth IEEE International Workshops, 308-313.
44. Penttinen, M. and Mikkonen, T. (2012), Subcontracting for Scrum Teams: Experiences and Guidelines from a Large Development Organization, 2012 IEEE Seventh International Conference on Global Software Engineering, 195-199.
45. Pikkarainen, M., Haikara, J., Salo, O., Abrahamsson, P., & Still, J. (2008), The impact of agile practices on communication in software development. Empirical Software Engineering, 13(3), 303-337.
46. Popli, R. and Chauhan, N. (2013), Information Systems and Computer Networks (ISCON), 2013 International Conference on IEEE, 98-103.
47. Rizwan Jameel Qureshi, M. (2012), Agile software development methodology for medium and large projects, Software, IET, Volume 6, Issue 4, 358-363.
48. Schwaber, K., & Beedle, M. (2002). gilè Software Development with Scrum.
49. Sliger, M., Broderick, S. (2008), The Software Project Manager′s Bridge to Agility Paperback, 1 Edition, MA:Pearson Education.
50. Sohaib, O., Khan, K.(2010), Integrating usability engineering and agile software development: A literature review, 2010 International Conference On Computer Design And Appliations (ICCDA 2010), Volume 2, 32-38.
51. Sonnentag, S., Volmer, J., (2009). Individual-level predictors of task-related teamwork processes: the role of expertise and selfefficacy in team meetings. Group & Organization Management 34 (1), 37–66.
52. Sultania, A. K. (2015), Developing software product and test automation software using Agile methodology. In Computer, Communication, Control and Information Technology (C3IT), 2015 Third International Conference on IEEE, 1-4.
53. Sutherland, J., Harrison, N., & Riddle, J. (2014). Teams that Finish Early Accelerate Faster: A Pattern Language for High Performing Scrum Teams. In System Sciences (HICSS), 2014 47th Hawaii International Conference on IEEE, 4722-4728.
54. Thakur, S. and Singh, H. (2014), FDRD: Feature driven reuse development process model, Advanced Communication Control and Computing Technologies (ICACCCT), 2014 International Conference on IEEE, 1593-1598.
55. The Standish Group International. The Standish Group′s CHAOS Report 2004. West Yarmouth, MA:The Standish Group, 2005.
56. Vlaanderen, K., Brinkkemper, S., Jansen, S., Jaspers, E. (2011), The agile requirements refinery: Applying SCRUM principles to software product management, Information and Software Technology on Elsevier, Volume 53, Issue 1, 58–70.
57. Weitzel, B., Rost, D., & Scheffe, M. (2014), Sustaining Agility through Architecture: Experiences from a Joint Research and Development Laboratory. In Software Architecture (WICSA), 2014 IEEE/IFIP Conference on IEEE, 53-56.
58. Williams, L. and Cockburn, A. (2003), Agile software development: it’s about feedback and change, Computer, 36( 6), 39–43.
59. Xu, B. (2009), Towards High Quality Software Development with Extreme Programming Methodology: Practices from Real Software Projects, Management and Service Science, 2009. MASS ′09. International Conference on IEEE, 1-4.
60. Yates, J.A., Orlikowski, W.J., (1992). Genres of organizational communication: a structurational approach to studying communication and media. Academy Management Review 17 (2), 299–326.
61. Yin, R.K. (2008). Case Study Research: Design and Methods: Design and Methods. Vol. 5. Sage Publications.
62. Yoshioka, T., Herman, G., Yates, J., Orlikowski, W.J., (2001). Genre taxonomy: a knowledge repository of communicative actions. ACM Transactions on Information Systems 19 (4), 431–456.
63. Ziółkowski, A., Deręgowski, T. (2014), Hybrid Approach in Project Management – Mixing Capability Maturity Model Integration with Agile Practices, Issn 1392-0758 Social Sciences. 2014. Nr. 3(85), 64-71.

指導教授

陳仲儼(Chung-Yang Chen)

審核日期

2016-6-7

推文