隨著現今使用者的需求逐漸多元且變動更加快速，敏捷軟體開發方法逐漸轉變為軟體開發者主要使用的軟體開發方法，因應敏捷軟體開發方法的普及，許多研究針對敏捷軟體專案關鍵成功、失敗因子進行探討，以提供實務上提升敏捷軟體專案績效之參考。現今敏捷軟體專案績效的研究中，並未有學者針對敏捷軟體專案績效因子之間的因果關係進行探討，因此本研究蒐集敏捷軟體專案績效影響因子，探討因子之間的相互影響關係，並提出敏捷軟體專案績效之關鍵影響因子，以提供以因果關係為基礎之敏捷軟體專案績效評估方法。
本研究以文獻分析法定義敏捷軟體專案績效為「在預定的時程與成本下交付對使用者有價值的軟體」，並蒐集敏捷專案關鍵成功因子、關鍵失敗因子與挑戰等研究，彙整出四個面向16個影響因子。再以專家量化問卷的形式蒐集10份專家評估資料，使用決策實驗室分析法(Decision Making Trial and Evaluation Laboratory, DEMATEL)探討影響因子間的因果關係。
根據本研究之分析結果，敏捷概念認知、多元的團隊溝通管道、客戶持續參與為敏捷軟體專案績效之關鍵影響因子，其次為管理層參與、團隊大小與複雜度、成員自主性以及輔助工具的採用，而效率的溝通、知識分享與傳遞、穩定的開發步調、優先排序與排程為關鍵被影響因子。此外，組織面向為影響敏捷軟體專案績效整體因果關係的根本原因，再延伸影響團隊與技術面向，最終影響流程面向。

As technology evolving, the need of user for newer innovations become more dynamic and diverse, customer preferences and needs also change more rapidly than ever before. Therefore, most of the software developers start to use agile as their software development method. There are many studies about the project success with agile, however, there are few studies discussing the relationships between agile project success factors. This study aims to explore (1) Factors in agile software project performance (2) Cause effect relationship between those factors (3) According to result above, find the critical cause factors of agile software project performance.
First, this study defines agile software project performance as “Deliver software that is valuable for users under predetermined schedule and cost.” Secondly, we collect three types of literature review, including agile critical success factors, agile critical failure factors, and agile challenges and limitations. Additionally, we design expert survey and collect ten samples. Finally, we use decision making trial and evaluation laboratory method(DEMATEL) to analyze the result.
According to the analysis result, we found that agile conceptual cognition, multiple team communication methods, and customer continuous involvement are the critical influence factors in agile software project performance, followed by management involvement, team size and complexity, member autonomy, and use of aid tools. Besides, effective communication, knowledge sharing and delivering, sustainable development, and prioritization and scheduling are critical influenced factors. Moreover, factors in organizational dimension seem as the root cause in total agile software project performance, those factors will influence factors in team and technical dimension, then will effect factors in process dimensions.

中文文獻
[1]. 周國村, & 袁建中. (2014). 應用決策實驗室分析 ((DEMATEL) 與網路層級分析法 (ANP) 在研發專案計畫評選. 中山管理評論, 22(3), 543-572.
[2]. 蔡清嵐. (2015). 應用決策實驗室分析法 (Dematel) 於企業雲端化移轉評估分析. 桃園創新學報(第 35).
[3]. 范雅琳. (2014). 基於能力與風險之供應商區隔. 臺北科技大學工業工程與管理系碩士班學位論文, 1-95.

英文文獻
[1]. Abdelaziz, A., Darwish, N., & Hefny, H. (2019). Multiple Linear Regression for Determining Critical Failure Factors of Agile Software Projects. International Journal of Intelligent Engineering and Systems, 12(3), 244-255. https://doi.org/10.22266/ijies2019.0630.24
[2]. Abrahamsson, P., Salo, O., Ronkainen, J., & Warsta, J. (2017). Agile software development methods: Review and analysis. arXiv preprint arXiv:1709.08439.
[3]. Ahimbisibwe, A., Cavana, R. Y., & Daellenbach, U. (2015). A contingency fit model of critical success factors for software development projects. Journal of Enterprise Information Management, 28(1), 7-33. https://doi.org/10.1108/jeim-08-2013-0060
[4]. Ahmad, M. O., Dennehy, D., Conboy, K., & Oivo, M. (2018). Kanban in software engineering: A systematic mapping study. Journal of Systems and Software, 137, 96-113. https://doi.org/10.1016/j.jss.2017.11.045
[5]. Aldahmash, A., Gravell, A. M., & Howard, Y. (2017). A Review on the Critical Success Factors of Agile Software Development. In Systems, Software and Services Process Improvement (pp. 504-512). https://doi.org/10.1007/978-3-319-64218-5_41
[6]. Ambler, S. (2007). Disciplined Agile Software Development: Definition. http://www.agilemodeling.com/essays/agileSoftwareDevelopment.htm.
[7]. Anwer, F., Aftab, S., Waheed, U., & Muhammad, S. (2017). Agile Software Development Models TDD, FDD, DSDM, and Crystal Methods: A Survey. International Journal of Multidisciplinary Sciences and Engineering, 8, 1-10.
[8]. Atkinson, R. (1999). Project management: cost, time and quality, two best guesses and a phenomenon, its time to accept other success criteria. International Journal of Project Management, 17(6), 337-342.
[9]. Badewi, A. (2016). The impact of project management (PM) and benefits management (BM) practices on project success: Towards developing a project benefits governance framework. International Journal of Project Management, 34(4), 761-778.
[10]. Beck, K., Beedle, M.,Bennekum, A., Cockburn, A, Cunningham, W.,Fowler, E.,Grenning, J.,Highsmith, J.,Hunt, A.,Jeffries, R.,Kern, J.,Marick, B.,Martin, R.,Mellor, S.,Schwaber, K.,Sutherland, J.,Thomas, D. (2001). Agile Manifesto. Agile Alliance. http://agilemanifesto.org/
[11]. Bergmann, T., & Karwowski, W. (2018). Agile project management and project success: A literature review. International Conference on Applied Human Factors and Ergonomics,
[12]. Boehm, B. (2007). A survey of agile development methodologies. Laurie Williams, 45, 119.
[13]. Chau, K. W. (2004). A two-stage dynamic model on allocation of construction facilities with genetic algorithm. Automation in construction, 13(4), 481-490.
[14]. Chiu, Y.-J., Chen, H.-C., Tzeng, G.-H., & Shyu, J. Z. (2006). Marketing strategy based on customer behaviour for the LCD-TV. International journal of management and decision making, 7(2-3), 143-165.
[15]. Cho, J. (2008). Issues and Challenges of agile software development with SCRUM. Issues in Information Systems, 9(2), 188-195.
[16]. Chow, T., & Cao, D.-B. (2008). A survey study of critical success factors in agile software projects. Journal of Systems and Software, 81(6), 961-971. https://doi.org/10.1016/j.jss.2007.08.020
[17]. Cline, A. (2015). Agile development in the real world. Springer.
[18]. Cohen, D., Lindvall, M., & Costa, P. (2004). An introduction to agile methods. Adv. Computer., 62(03), 1-66.
[19]. Cohn, M., & Ford, D. (2003). Introducing an agile process to an organization software development. Computer, 36(6), 74-78.
[20]. Cooke-Davies, T. (2002). The “real” success factors on projects. International Journal of Project Management, 20(3), 185-190. https://doi.org/10.1016/s0263-7863(01)00067-9
[21]. Darwish, N. R., Mohamed, A. A., & Abdelghany, A. S. (2016). A hybrid machine learning model for selecting suitable requirements elicitation techniques. International Journal of Computer Science and Information Security, 14(6), 1-12.
[22]. De Wit, A. (1988). Measurement of project success. International Journal of Project Management, 6(3), 164-170. https://doi.org/10.1016/0263-7863(88)90043-9
[23]. Deephouse, C., Mukhopadhyay, T., Goldenson, D. R., & Kellner, M. I. (1995). Software Processes and Project Performance. Journal of Management Information Systems, 12(3), 187-205. https://doi.org/10.1080/07421222.1995.11518097
[24]. Dhir, S., Kumar, D., & Singh, V. B. (2019). Success and Failure Factors that Impact on Project Implementation Using Agile Software Development Methodology. In (pp. 647-654). Springer Singapore. https://doi.org/10.1007/978-981-10-8848-3_62
[25]. Dikert, K., Paasivaara, M., & Lassenius, C. (2016). Challenges and success factors for large-scale agile transformations: A systematic literature review. Journal of Systems and Software, 119, 87-108.
[26]. Dima, A. M., & Maassen, M. A. (2018). From Waterfall to Agile software: Development models in the IT sector, 2006 to 2018. Impacts on company management. Journal of International Studies, 11(2), 315-326.
[27]. Drury-Grogan, M. L. (2014). Performance on agile teams: Relating iteration objectives and critical decisions to project management success factors. Information and Software Technology, 56(5), 506-515. https://doi.org/10.1016/j.infsof.2013.11.003
[28]. Dybå, T., & Dingsøyr, T. (2008). Empirical studies of agile software development: A systematic review. Information and Software Technology, 50(9-10), 833-859. https://doi.org/10.1016/j.infsof.2008.01.006
[29]. Fekri, R., Aliahmadi, A., & Fathian, M. (2009). Identifying the cause and effect factors of agile NPD process with fuzzy DEMATEL method: the case of Iranian companies. Journal of Intelligent Manufacturing, 20(6), 637.
[30]. Fontela, E., & Gabus, A. (1976). The DEMATEL observer. In DEMATEL 1976 Report. Switzerland Geneva: Battelle Geneva Research Center.
[31]. Fowler, M. (2002). The Agile Manifesto: where it came from and where it may go. Published on the Internet in February.
[32]. Fowler, M., & Highsmith, J. (2001). The agile manifesto. Software development, 9(8), 28-35.
[33]. Gandomani, T. J., Zulzalil, H., Ghani, A. A. A., Sultan, A. B. M., & Parizi, R. M. (2015). The impact of inadequate and dysfunctional training on Agile transformation process: a Grounded Theory study. Information and Software Technology, 57, 295-309.
[34]. Gregory, P., Barroca, L., Sharp, H., Deshpande, A., & Taylor, K. (2016). The challenges that challenge: Engaging with agile practitioners’ concerns. Information and Software Technology, 77, 92-104. https://doi.org/10.1016/j.infsof.2016.04.006
[35]. Hastie, S., & Engineer, C. K. (2004). The Agile Mindset: what does it take to make this stuff work? Software Education Associates Ltd, Agile Development Conference Wellington & Sydney,
[36]. Haverila, M. J., & Fehr, K. (2016). The impact of product superiority on customer satisfaction in project management. International Journal of Project Management, 34(4), 570-583.
[37]. Highsmith, J., & Cockburn, A. (2001). Agile software development: The business of innovation. Computer, 34(9), 120-127.
[38]. Hirsch, M. (2005). Moving from a plan driven culture to agile development. International Conference on Software Engineering,
[39]. Hoda, R., & Murugesan, L. K. (2016). Multi-level agile project management challenges: A self-organizing team perspective. Journal of Systems and Software, 117, 245-257. https://doi.org/https://doi.org/10.1016/j.jss.2016.02.049
[40]. Hoda, R., Noble, J., & Marshall, S. (2008). Agile project management. New Zealand computer science research student conference,
[41]. Hori, S., & Shimizu, Y. (1999). Designing methods of human interface for supervisory control systems. Control engineering practice, 7(11), 1413-1419.
[42]. Institute, P. M. (2017). A guide to the Project Management Body of Knowledge (PMBOK guide) (6th ed. ed.).
[43]. International, S. G. (2015). The chaos report. United States of America.
[44]. Jovanović, M., Mesquida, A., Mas, A., & Colomo-Palacios, R. (2020). Agile Transition and Adoption Frameworks, Issues and Factors: A Systematic Mapping. Ieee Access, 15711-15735. https://doi.org/10.1109/ACCESS.2020.2967839
[45]. Jugdev, K., & Müller, R. (2005). A retrospective look at our evolving understanding of project success. Project Management Journal, 36(4), 19-31.
[46]. Kalermo, J., & Rissanen, J. (2002). Agile software development in theory and practice.
[47]. Kniberg, H., & Skarin, M. (2010). Kanban and Scrum-making the most of both..
[48]. Koi-Akrofi, G. Y., Akrofi, J. K., & Akwetey Matey, H. (2019). Understanding the Characteristics, Benefits and Challenges of Agile it Project Management: A Literature Based Perspective. International Journal of Software Engineering & Applications, 10(5), 25-44. https://doi.org/10.5121/ijsea.2019.10502
[49]. Kumar, R., Maheshwary, P., & Malche, T. (2019). Inside agile family software development methodologies. International Journal of Computer Sciences and Engineering, 7(6), 650-660.
[50]. Kurup, D., & Sidhardhan, S. K. (2015). Agile Project Management–Benefits and Challenges. Academia.[Online]
[51]. Laanti, M., Similä, J., & Abrahamsson, P. (2013). Definitions of Agile Software Development and Agility. In (pp. 247-258). Springer Berlin Heidelberg. https://doi.org/10.1007/978-3-642-39179-8_22
[52]. Lalonde, P.-L., Bourgault, M., & Findeli, A. (2010). Building pragmatist theories of PM practice: Theorizing the act of project management. Project Management Journal, 41(5), 21-36.
[53]. Larman, C., & Basili, V. R. (2003). Iterative and incremental developments. a brief history. Computer, 36(6), 47-56. https://doi.org/10.1109/mc.2003.1204375
[54]. Leau, Y. B., Loo, W. K., Tham, W. Y., & Tan, S. F. (2012). Software development life cycle AGILE vs traditional approaches. International Conference on Information and Network Technology,
[55]. Livermore, J. A. (2008). Factors that Significantly Impact the Implementation of an Agile Software Development Methodology. J. Softw., 3(4), 31-36.
[56]. McLeod, L., & Macdonell, S. G. (2011). Factors that affect software systems development project outcomes. ACM Computing Surveys, 43(4), 1-56. https://doi.org/10.1145/1978802.1978803
[57]. Meier, A., Kropp, M., & Perellano, G. (2016). Experience Report of Teaching Agile Collaboration and Values: Agile Software Development in Large Student Teams 2016 IEEE 29th International Conference on Software Engineering Education and Training (CSEET),
[58]. Meyer, B. (2014). Agile! Bertrand MeyerThe Good, the Hype and the Ugly. Springer.
[59]. Miklosik, A., Hvizdova, E., & Žák, Š. (2012). Scrum as the method supporting the implementation of knowledge management in an organization. International Journal of Social, Behavioral, Educational, Economic, Business and Industrial Engineering, 6, 6-9.
[60]. Miller, G. J. (2013). Agile problems, challenges, & failures.
[61]. Misra, S., Kumar, V., Kumar, U., Fantazy, K., & Akhter, M. (2012). Agile software development practices: evolution, principles, and criticisms. International Journal of Quality & Reliability Management, 29(9), 972-980. https://doi.org/10.1108/02656711211272863
[62]. Moe, N. B., Aurum, A., & Dybå, T. (2012). Challenges of shared decision-making: A multiple case study of agile software development. Information and Software Technology, 54(8), 853-865. https://doi.org/10.1016/j.infsof.2011.11.006
[63]. Munns, A. K., & Bjeirmi, B. F. (1996). The role of project management in achieving project success. International Journal of Project Management, 14(2), 81-87. https://doi.org/https://doi.org/10.1016/0263-7863(95)00057-7
[64]. Nerur, S., Mahapatra, R., & Mangalaraj, G. (2005). Challenges of migrating to agile methodologies. Communications of the ACM, 48(5), 72-78. https://doi.org/10.1145/1060710.1060712
[65]. Petersen, K., & Wohlin, C. (2010). The effect of moving from a plan-driven to an incremental software development approach with agile practices. Empirical Software Engineering, 15(6), 654-693.
[66]. Ren, J., Manzardo, A., Toniolo, S., & Scipioni, A. (2013). Sustainability of hydrogen supply chain. Part I: Identification of critical criteria and cause–effect analysis for enhancing the sustainability using DEMATEL. International Journal of Hydrogen Energy, 38(33), 14159-14171. https://doi.org/10.1016/j.ijhydene.2013.08.126
[67]. Ribeiro, P., Paiva, A., Varajão, J., & Dominguez, C. (2013). Success evaluation factors in construction project management—some evidence from medium and large Portuguese companies. KSCE Journal of Civil Engineering, 17(4), 603-609.
[68]. Royce, W. W. (1987). Managing the development of large software systems: concepts and techniques. Proceedings of the 9th international conference on Software Engineering,
[69]. Söderlund, J. (2004). Building theories of project management: past research, questions for the future. International Journal of Project Management, 22(3), 183-191. https://doi.org/10.1016/s0263-7863(03)00070-x
[70]. Shameem, M., Kumar, R. R., Kumar, C., Chandra, B., & Khan, A. A. (2018). Prioritizing challenges of agile process in distributed software development environment using analytic hierarchy process. Journal of Software: Evolution and Process, 30(11), e1979. https://doi.org/10.1002/smr.1979
[71]. Sharma, S., & Hasteer, N. (2016). A comprehensive study on state of Scrum development. 2016 International Conference on Computing, Communication and Automation (ICCCA),
[72]. Si, S.-L., You, X.-Y., Liu, H.-C., & Zhang, P. (2018). DEMATEL Technique: A Systematic Review of the State-of-the-Art Literature on Methodologies and Applications. Mathematical Problems in Engineering, 2018, 1-33. https://doi.org/10.1155/2018/3696457
[73]. Singh, V., Gu, N., & Wang, X. (2011). A theoretical framework of a BIM-based multi-disciplinary collaboration platform. Automation in construction, 20(2), 134-144.
[74]. Sithambaram, J., Nasir, M. H. N. B. M., & Ahmad, R. (2021). Issues and challenges impacting the successful management of agile-hybrid projects: A grounded theory approach. International Journal of Project Management. https://doi.org/10.1016/j.ijproman.2021.03.002
[75]. Solinski, A., & Petersen, K. (2016). Prioritizing agile benefits and limitations in relation to practice usage. Software Quality Journal, 24(2), 447-482.
[76]. Sommerville, I. (2016). Software Engineering (t. ed., Ed. ed.).
[77]. Stoica, M., Ghilic-Micu, B., Mircea, M., & Uscatu, C. (2016). Analyzing Agile Development – from Waterfall Style to Scrumban. Informatica Economica, 20(4/2016), 5-14. https://doi.org/10.12948/issn14531305/20.4.2016.01
[78]. Tam, C., Moura, E. J. D. C., Oliveira, T., & Varajão, J. (2020). The factors influencing the success of on-going agile software development projects. International Journal of Project Management, 38(3), 165-176. https://doi.org/10.1016/j.ijproman.2020.02.001
[79]. Tarhan, A., & Yilmaz, S. G. (2014). Systematic analyses and comparison of development performance and product quality of Incremental Process and Agile Process. Information and Software Technology, 56(5), 477-494.
[80]. Tolvanen, J.-P. (1998). Incremental method engineering with modeling tools: theoretical principles and empirical evidence. Ph. D. Thesis, University of Jyvaskyla.
[81]. Van Wyngaard, C. J., Pretorius, J. H. C., & Pretorius, L. (2012). Theory of the triple constraint — A conceptual review.
[82]. VanderLeest, S. H., & Buter, A. (2009). Escape the waterfall: Agile for aerospace. 2009 IEEE/AIAA 28th Digital Avionics Systems Conference,
[83]. VersionOne. (2020). 14th Annual state of agile report. Version One.
[84]. VersionOne. (2021). 15th Annual state of agile report. Version One.
[85]. Williams, L. (2012). What agile teams think of agile principles. Communications of the ACM, 55(4), 71-76. https://doi.org/10.1145/2133806.2133823
[86]. Williams, L., & Cockburn, A. (2003). Guest Editors' Introduction: Agile Software Development: It? s about Feedback and Change. Computer, 36(06), 39-43.
[87]. Williams, L., Rubin, K., & Cohn, M. (2010). Driving process improvement via comparative agility assessment. 2010 Agile Conference,
[88]. Wu, W.-W., & Lee, Y.-T. (2007). Selecting knowledge management strategies by using the analytic network process. Expert Systems with Applications, 32(3), 841-847.
[89]. Wu, W.-Y., Sukoco, B. M., Li, C.-Y., & Chen, S. H. (2009). An integrated multi-objective decision-making process for supplier selection with bundling problem. Expert Systems with Applications, 36(2), 2327-2337.