Journal of Intelligence and Information Systems (지능정보연구)

Korea Intelligent Information System Society (한국지능정보시스템학회)
권호 표지
DOI QR코드

DOI QR Code

The Role of Clients in Software Projects with Agile Methods

애자일 방법론을 사용한 소프트웨어 프로젝트에서의 사용자 역할 분석

  • Received : 2019.05.20
  • Accepted : 2019.08.16
  • Published : 2019.09.30
Download PDF
⟨ Previous Next ⟩

Abstract

Agile methodologies in software development, including the development of artificial intelligence software, have been widespread over the past several years. In spite of the popularity of agile methodologies in practice, there is a lack of empirical evidence to identify determinants of success of software projects in which agile methods are used. To understand the role of clients in software project where agile methods are used, we examine the effect of client-side factors, including lack of user involvement, unrealistic client expectations, and constant changes of requirements on project success from practitioners' perspective. Survey methods are used in this study. Data were collected by means of online survey to IT professionals who have experience with software development methodologies, and ordered logit regression is used to analyze the survey data. Results of our study imply the following managerial findings. First, user involvement is critical to project success to take advantage of agile methods. Second, it is interesting that, with an agile method, constant changes of client's requirements is not a negative factor but a positive factor of project success. Third, unrealistic client expectations do negatively affect project success even with agile methods.

애자일 방법론은 인공지능 소프트웨어를 포함한 소프트웨어 개발 프로젝트에서 지난 몇 년 동안 널리 사용되고 있다. 이처럼 산업에서 애자일 방법론이 많이 사용되고 있음에도 불구하고, 애자일 방법론을 사용하는 소프트웨어 프로젝트의 성공 요인을 분석한 실증적 연구가 부족한 실정이다. 애자일 방법론을 사용하는 소프트웨어 프로젝트에서 고객의 역할을 이해하기 위해 사용자 참여 부족, 비현실적인 고객 기대치, 지속적인 요구 사항 변경의 고객 측 요인들이 프로젝트 성공에 미치는 영향을 조사하였다. 본 연구의 분석 대상은 애자일 방법을 소프트웨어 개발 방법론으로 사용하는 프로젝트이다. 일반적으로 소프트웨어 개발에서의 주 목표는 적은 시간과 비용으로 고품질 소프트웨어를 개발하는 것이다. 과거에는 프로젝트의 초기 단계에서 정한 고객 요구사항의 변화를 최소화하여, 그 변화에 수반되는 비용을 줄이려고 했다면, 오늘날의 프로젝트 관리에서 고객 요구사항의 변화는 고객이 원하는 시스템 개발을 위해 필수적인 것이라 인정하고 이 불가피한 변화에 보다 잘 대응하는 것이 중요하다고 볼 수 있다. 이에 효과적인 방법론으로 애자일 방법론이 많이 사용되고 있고, 본 연구에서는 이 애자일 방법론을 사용하는 프로젝트의 성공요인을 찾아내고자 한다. 본 연구를 위해 설문 방법이 이용되었다. 소셜 네트워크 사이트인 링크드인(LinkedIn)을 이용하여 소프트웨어 프로젝트 참여 경험이 있는 개발자들을 대상으로 온라인 설문을 하였고, 분석에 사용한 데이터는 213개의 응답 데이터이다. 이 설문 응답 데이터를 Ordered Logit Regression을 이용하여 세 가지 가설을 검증하였다. 분석 결과, 위 세 가지 클라이언트 측 요인들 모두가 애자일 방법을 사용하는 프로젝트의 성공에 크게 영향을 미친다는 사실을 실증적으로 찾아내었다. 첫째, 애자일 방법을 이용하기 위해서는 고객의 프로젝트 참여가 필수적이다. 이 결과는 애자일 방법론의 이론적 효과와 일치한다. 사용자와의 협업이 애자일 방법론에서 가장 중요한 요소 중에 하나인 만큼 고객의 참여는 매우 중요하다고 볼 수 있다. 둘째, 애자일 방법이 사용된 프로젝트에서는 고객의 요구 사항을 지속적으로 변경하는 것이 부정적인 요인이 아니라 프로젝트 성공의 긍정적인 요인이라는 흥미로운 결과를 얻었다. 고객의 요구 사항을 지속적으로 변경하는 것은 클라이언트와 공급 업체 간의 빈번한 상호 작용이나 의사 소통을 통해 사용자가 진정으로 원하는 시스템을 만드는데 도움이 되어 긍정적인 요인이 된다는 설명이 가능하다. 셋째, 비현실적인 고객의 기대는 애자일 방법이 사용된 프로젝트에서도 프로젝트 성공에 부정적인 영향을 준다는 결과를 얻었다.

Keywords

References

  1. Abdel-Hamid, T. K., K. Sengupta, and C. Swett. "The Impact of Goals on Software Project Management: An Experimental Investigation." Mis Quarterly, Vol. (1999), 531-55.
  2. Abrahamsson, P. S. O. R. J. and J. Warsta. "Agile Software Development Methods: Review and Analysis." Espoo, Finland: Technical Research Centre of Finland, VTT Publications, Vol. (2002), 478.
  3. Ahimbisibwe, A., R. Y. Cavana, and U. Daellenbach. "A Contingency Fit Model of Critical Success Factors for Software Development Projects: A Comparison of Agile and Traditional Plan-Based Methodologies." Journal of Enterprise Information Management, Vol. 28, No. 1(2015), 7-33. https://doi.org/10.1108/JEIM-08-2013-0060
  4. Ahimbisibwe, A., U. Daellenbach, and R. Y. Cavana. "Empirical Comparison of Traditional Plan-Based and Agile Methodologies: Critical Success Factors for Outsourced Software Development Projects from Vendors' Perspective." Journal of Enterprise Information Management, Vol. 30, No. 3(2017), 400-53. https://doi.org/10.1108/JEIM-06-2015-0056
  5. Atkinson, R. "Project Management: Cost, Time and Quality, Two Best Guesses and a Phenomenon, Its Time to Accept Other Success Criteria." International Journal of Project Management, Vol. 17, No. 6(1999), 337-42. https://doi.org/10.1016/S0263-7863(98)00069-6
  6. Baccarini, D. "The Logical Framework Method for Defining Project Success." Project Management Journal, Vol. 30, No. 4(1999), 25-32. https://doi.org/10.1177/875697289903000405
  7. Baccarini, D. "The Logical Framework Method for Defining Project Success." Project Management Journal, Vol. 30, No. 4(1999), 25-32. https://doi.org/10.1177/875697289903000405
  8. Beck, K. Extreme Programming Explained: Embrace Change: addison-wesley professional, 2000.
  9. Belassi, W. and O. I. Tukel. "A New Framework for Determining Critical Success/Failure Factors in Projects." International Journal of Project Management, Vol. 14, No. 3(1996), 141-51. https://doi.org/10.1016/0263-7863(95)00064-X
  10. Bennatan, E. M. On Time within Budget: John Wiley and Sons, 2000.
  11. Blaskovics, B. "The Impact of Project Manager on Project Success-the Case of Ict Sector." Society and Economy in Central and Eastern Europe, Vol. 38, No. 2(2016), 261-81.
  12. Boehm, B. "Get Ready for Agile Methods, with Care." Computer, Vol. 35, No. 1(2002), 64-69. https://doi.org/10.1109/2.976920
  13. Boehm, B. W. "Software Engineering: R & D Trends and Defense Needs. Research Directions in Software Technology." MIT Press: Cambridge MA, Vol. (1979).
  14. Boehm, B. W. "Software Risk Management: Principles and Practices." IEEE Software, Vol. 8, No. 1(1991), 32-41. https://doi.org/10.1109/52.62930
  15. Briner, W., M. Geddes, and C. Hastings. Project Leadership: Gower Publishing Company, Limited, 1993.
  16. Brooks Jr, F. P. The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition, 2/E: Pearson Education India, 1995.
  17. Chow, T. and D.-B. Cao. "A Survey Study of Critical Success Factors in Agile Software Projects." Journal of Systems and Software, Vol. 81, No. 6(2008), 961-71. https://doi.org/10.1016/j.jss.2007.08.020
  18. Cockburn, A. and J. Highsmith. "Agile Software Development, the People Factor." Computer, Vol. 34, No. 11(2001), 131-33. https://doi.org/10.1109/2.963450
  19. Coram, M. and S. Bohne. "The Impact of Agile Methods on Software Project Management." Paper presented at the 12th IEEE International Conference and Workshops on the Engineering of Computer-Based Systems, 2005.
  20. Couger, J. D. "Motivators Vs. Demotivators in the Is Environment." Journal of Systems Management, Vol. 39, No. 6(1988), 36.
  21. De Roze, B. C. and T. H. Nyman. "The Software Life Cycle-a Management and Technological Challenge in the Department of Defense." Ieee Transactions on Software Engineering, Vol., No. 4(1978), 309-18.
  22. DeCotiis, T. A. and L. Dyer. "Defining and Measuring Project Performance." Research Management, Vol. 22, No. 1(1979), 17-22. https://doi.org/10.1080/00345334.1979.11756516
  23. DeMarco, T. Controlling Software Projects: Management, Measurement, and Estimates, Prentice Hall PTR, 1986.
  24. Dvir, D., S. Lipovetsky, A. Shenhar, and A. Tishler. "In Search of Project Classification: A Non-Universal Approach to Project Success Factors." Research Policy, Vol. 27, No. 9(1998), 915-35. https://doi.org/10.1016/S0048-7333(98)00085-7
  25. Fan, D. "Analysis of Critical Success Factors in It Project Management." Paper presented at the Industrial and Information Systems (IIS), 2010 2nd International Conference on 2010.
  26. Fortune, J. and D. White. "Framing of Project Critical Success Factors by a Systems Model." International Journal of Project Management, Vol. 24, No. 1(2006), 53-65. https://doi.org/10.1016/j.ijproman.2005.07.004
  27. Fowler, M. and J. Highsmith. "The Agile Manifesto." Software Development 2001, 28-35.
  28. Greene, W. H. Econometric Analysis. Upper Saddle River, New Jersey: Prentice Hall, 2000.
  29. Hackman, J. R. and G. R. Oldham. "Work Redesign (Vol. 72)." Reading: Addison-Wesley, Vol. (1980).
  30. Highsmith, J. "Agile Project Management: Principles and Tools." Cutter consortium, Vol. 4(2003), 1-37.
  31. Highsmith, J. and A. Cockburn. "Agile Software Development: The Business of Innovation." Computer, Vol. 34, No. 9(2001), 120-27. https://doi.org/10.1109/2.947100
  32. Holmstrom, H., B. Fitzgerald, P. J. Agerfalk, and E. O. Conchuir. "Agile Practices Reduce Distance in Global Software Development." Information systems management, Vol. 23, No. 3(2006), 7-18. https://doi.org/10.1201/1078.10580530/46108.23.3.20060601/93703.2
  33. Janzen, D. and H. Saiedian. "Test-Driven Development Concepts, Taxonomy, and Future Direction." Computer, Vol. 38, No. 9(2005), 43-50. https://doi.org/10.1109/MC.2005.314
  34. Kanter, R. M. "Three Tiers for Innovation Research." Communication Research, Vol. 15, No. 5(1988), 509-23. https://doi.org/10.1177/009365088015005001
  35. Kniberg, H. and M. Skarin. Kanban and Scrum-Making the Most of Both: Lulu.com, 2010.
  36. Linberg, K. R. "Software Developer Perceptions About Software Project Failure: A Case Study." Journal of Systems and Software, Vol. 49, No. 2(1999), 177-92. https://doi.org/10.1016/S0164-1212(99)00094-1
  37. Lindstrom, L. and R. Jeffries. "Extreme Programming and Agile Software Development Methodologies." Information systems management, Vol. 21, No. 3(2004), 41-52. https://doi.org/10.1201/1078/44432.21.3.20040601/82476.7
  38. Loforte Ribeiro, F. and M. Timoteo Fernandes. "Exploring Agile Methods in Construction Small and Medium Enterprises: A Case Study." Journal of Enterprise Information Management, Vol. 23, No. 2(2010), 161-80. https://doi.org/10.1108/17410391011019750
  39. McCullagh, P. "Regression Models for Ordinal Data." Journal of the Royal Statistical Society: Series B (Methodological), Vol. 42, No. 2(1980), 109-27. https://doi.org/10.1111/j.2517-6161.1980.tb01109.x
  40. Misra, S. C., V. Kumar, and U. Kumar. "Identifying Some Important Success Factors in Adopting Agile Software Development Practices." Journal of Systems and Software, Vol. 82, No. 11(2009), 1869-90. https://doi.org/10.1016/j.jss.2009.05.052
  41. Morris, Peter WG, and George H. Hough. "The anatomy of major projects: A study of the reality of project management." (1987).
  42. Myers, M. D. "Dialectical Hermeneutics: A Theoretical Framework for the Implementation of Information Systems." Information Systems Journal, Vol. 5, No. 1(1995), 51-70. https://doi.org/10.1111/j.1365-2575.1995.tb00089.x
  43. Naquin, C. E. and R. O. Tynan. "The Team Halo Effect: Why Teams Are Not Blamed for Their Failures." Journal of Applied Psychology, Vol. 88, No. 2(2003), 332. https://doi.org/10.1037/0021-9010.88.2.332
  44. Pereira, J., N. Cerpa, J. Verner, M. Rivas, and J. D. Procaccino. "What Do Software Practitioners Really Think About Project Success: A Cross-Cultural Comparison." Journal of Systems and Software, Vol. 81, No. 6(2008), 897-907. https://doi.org/10.1016/j.jss.2007.07.032
  45. Phan, D., D. Vogel, and J. Nunamaker. "The Search for Perfect Project Management." Computerworld, Vol. 22, No. 39(1988), 95-100.
  46. Pinto, J. K. and S. J. Mantel. "The Causes of Project Failure." Ieee Transactions on Engineering Management, Vol. 37, No. 4(1990), 269-76. https://doi.org/10.1109/17.62322
  47. Pinto, J. K. and D. P. Slevin. Critical Success Factors in Effective Project Implementation. Vol. 479, Project Management Handbook, CRC Press, 1988.
  48. Poon, P. and C. Wagner. "Critical Success Factors Revisited: Success and Failure Cases of Information Systems for Senior Executives." Decision Support Systems, Vol. 30, No. 4(2001), 393-418. https://doi.org/10.1016/S0167-9236(00)00069-5
  49. Procaccino, J. D. and J. M. Verner. "Software Practitioner's Perception of Project Success: A Pilot Study." International Journal of Computers.The Internet and Management, Vol. 10, No. 1(2002), 20-30.
  50. Procaccino, J. D. and J. M. Verner. "Software Project Managers and Project Success: An Exploratory Study." Journal of Systems and Software, Vol. 79, No. 11(2006), 1541-51. https://doi.org/10.1016/j.jss.2006.01.010
  51. Purna Sudhakar, G. "A Model of Critical Success Factors for Software Projects." Journal of Enterprise Information Management, Vol. 25, No. 6(2012), 537-58. https://doi.org/10.1108/17410391211272829
  52. Redmill, F. J. "Considering Quality in the Management of Software-Based Development Projects." Information and Software Technology, Vol. 32, No. 1(1990), 18-22. https://doi.org/10.1016/0950-5849(90)90041-O
  53. Reel, J. S. "Critical Success Factors in Software Projects." IEEE Software, Vol. 16, No. 3(1999), 18-23. https://doi.org/10.1109/52.765782
  54. Remenyi, D. and M. Sherwood-Smith. "Maximise Information Systems Value by Continuous Participative Evaluation." Logistics Information Management, Vol. 12, No. 1/2(1999), 14-31. https://doi.org/10.1108/09576059910256222
  55. Rook, P. "Controlling Software Projects." Software Engineering Journal, Vol. 1, No. 1(1986), 7-16. https://doi.org/10.1049/sej.1986.0003
  56. Royce, W. "The Software Lifecycle Model (Waterfall Model)." Paper presented at the Proc. WESTCON 1970.
  57. Saarinen, T. "An Expanded Instrument for Evaluating Information System Success." Information & management, Vol. 31, No. 2(1996), 103-18. https://doi.org/10.1016/S0378-7206(96)01075-0
  58. Salmeron, J. L. and I. Herrero. "An Ahp-Based Methodology to Rank Critical Success Factors of Executive Information Systems." Computer Standards & Interfaces, Vol. 28, No. 1(2005), 1-12. https://doi.org/10.1016/j.csi.2004.09.002
  59. Selin, G. "Organizational Support: Building a Framework for Project Success Pmi Seminar." 1989.
  60. Serrador, P. and J. K. Pinto. "Does Agile Work?-a Quantitative Analysis of Agile Project Success." International Journal of Project Management, Vol. 33, No. 5(2015), 1040-51. https://doi.org/10.1016/j.ijproman.2015.01.006
  61. Session, H. "Leadership in Real Time: A Model of Five Levels of Attributes Needed by a Project Manager in Erp Implementations." Vol. (2003).
  62. Szajna, B. and R. W. Scamell. "The Effects of Information System User Expectations on Their Performance and Perceptions." Mis Quarterly, Vol. (1993), 493-516.
  63. Wallace, D. "Get It Done." Project management your most valuable tool.Success, Vol. 30(1990), 46-47.
  64. Walsh, K. R. and H. Schneider. "The Role of Motivation and Risk Behaviour in Software Development Success." Information research, Vol. 7, No. 3(2002), 15.
  65. Wateridge, J. "How Can Is/It Projects Be Measured for Success?" International Journal of Project Management, Vol. 16, No. 1(1998), 59-63. https://doi.org/10.1016/S0263-7863(97)00022-7
  66. Wateridge, J. "IT Projects: A Basis for Success." International Journal of Project Management, Vol. 13, No. 3(1995), 169-72. https://doi.org/10.1016/0263-7863(95)00020-Q
  67. Weltz, L. "How to Implement Projects Successfully." Software Magazine, Vol. 9(1989), 13.
  68. Williams, R. "Generalized Ordered Logit/Partial Proportional Odds Models for Ordinal Dependent Variables." Stata Journal, Vol. 6, No. 1(2006), 58-82. https://doi.org/10.1177/1536867X0600600104
  69. Wohlin, C. and A. A. Andrews. "Assessing Project Success Using Subjective Evaluation Factors." Software Quality Journal, Vol. 9, No. 1(2001), 43-70. https://doi.org/10.1023/A:1016673203332
  70. Wohlin, C., A. Von Mayrhauser, M. Host, and B. Regnell. "Subjective Evaluation as a Tool for Learning from Software Project Success." Information and Software Technology, Vol. 42, No. 14(2000), 983-92. https://doi.org/10.1016/S0950-5849(00)00150-6