Browse > Article
http://dx.doi.org/10.13088/jiis.2019.25.3.141

The Role of Clients in Software Projects with Agile Methods  

Kim, Vladimir (University of Seoul)
Cho, Wooje (University of Seoul)
Jung, Yoonhyuk (Korea University)
Publication Information
Journal of Intelligence and Information Systems / v.25, no.3, 2019 , pp. 141-160 More about this Journal
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.
Keywords
agile methodology; project success; project management; ordered logit regression; survey;
Citations & Related Records
연도 인용수 순위
  • Reference
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.   DOI
4 Pinto, J. K. and S. J. Mantel. "The Causes of Project Failure." Ieee Transactions on Engineering Management, Vol. 37, No. 4(1990), 269-76.   DOI
5 Pinto, J. K. and D. P. Slevin. Critical Success Factors in Effective Project Implementation. Vol. 479, Project Management Handbook, CRC Press, 1988.
6 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.   DOI
7 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.
8 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.   DOI
9 Purna Sudhakar, G. "A Model of Critical Success Factors for Software Projects." Journal of Enterprise Information Management, Vol. 25, No. 6(2012), 537-58.   DOI
10 Redmill, F. J. "Considering Quality in the Management of Software-Based Development Projects." Information and Software Technology, Vol. 32, No. 1(1990), 18-22.   DOI
11 Reel, J. S. "Critical Success Factors in Software Projects." IEEE Software, Vol. 16, No. 3(1999), 18-23.   DOI
12 Baccarini, D. "The Logical Framework Method for Defining Project Success." Project Management Journal, Vol. 30, No. 4(1999), 25-32.   DOI
13 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.   DOI
14 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.   DOI
15 Baccarini, D. "The Logical Framework Method for Defining Project Success." Project Management Journal, Vol. 30, No. 4(1999), 25-32.   DOI
16 Beck, K. Extreme Programming Explained: Embrace Change: addison-wesley professional, 2000.
17 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.   DOI
18 Bennatan, E. M. On Time within Budget: John Wiley and Sons, 2000.
19 Rook, P. "Controlling Software Projects." Software Engineering Journal, Vol. 1, No. 1(1986), 7-16.   DOI
20 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.   DOI
21 Royce, W. "The Software Lifecycle Model (Waterfall Model)." Paper presented at the Proc. WESTCON 1970.
22 Session, H. "Leadership in Real Time: A Model of Five Levels of Attributes Needed by a Project Manager in Erp Implementations." Vol. (2003).
23 Boehm, B. "Get Ready for Agile Methods, with Care." Computer, Vol. 35, No. 1(2002), 64-69.   DOI
24 Boehm, B. W. "Software Engineering: R & D Trends and Defense Needs. Research Directions in Software Technology." MIT Press: Cambridge MA, Vol. (1979).
25 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.   DOI
26 Selin, G. "Organizational Support: Building a Framework for Project Success Pmi Seminar." 1989.
27 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.   DOI
28 Szajna, B. and R. W. Scamell. "The Effects of Information System User Expectations on Their Performance and Perceptions." Mis Quarterly, Vol. (1993), 493-516.
29 Wallace, D. "Get It Done." Project management your most valuable tool.Success, Vol. 30(1990), 46-47.
30 Boehm, B. W. "Software Risk Management: Principles and Practices." IEEE Software, Vol. 8, No. 1(1991), 32-41.   DOI
31 Briner, W., M. Geddes, and C. Hastings. Project Leadership: Gower Publishing Company, Limited, 1993.
32 Brooks Jr, F. P. The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition, 2/E: Pearson Education India, 1995.
33 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.   DOI
34 Cockburn, A. and J. Highsmith. "Agile Software Development, the People Factor." Computer, Vol. 34, No. 11(2001), 131-33.   DOI
35 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.
36 Couger, J. D. "Motivators Vs. Demotivators in the Is Environment." Journal of Systems Management, Vol. 39, No. 6(1988), 36.
37 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.
38 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.
39 DeCotiis, T. A. and L. Dyer. "Defining and Measuring Project Performance." Research Management, Vol. 22, No. 1(1979), 17-22.   DOI
40 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.
41 Wateridge, J. "How Can Is/It Projects Be Measured for Success?" International Journal of Project Management, Vol. 16, No. 1(1998), 59-63.   DOI
42 Wateridge, J. "IT Projects: A Basis for Success." International Journal of Project Management, Vol. 13, No. 3(1995), 169-72.   DOI
43 Weltz, L. "How to Implement Projects Successfully." Software Magazine, Vol. 9(1989), 13.
44 Williams, R. "Generalized Ordered Logit/Partial Proportional Odds Models for Ordinal Dependent Variables." Stata Journal, Vol. 6, No. 1(2006), 58-82.   DOI
45 Saarinen, T. "An Expanded Instrument for Evaluating Information System Success." Information & management, Vol. 31, No. 2(1996), 103-18.   DOI
46 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.
47 Wohlin, C. and A. A. Andrews. "Assessing Project Success Using Subjective Evaluation Factors." Software Quality Journal, Vol. 9, No. 1(2001), 43-70.   DOI
48 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.   DOI
49 DeMarco, T. Controlling Software Projects: Management, Measurement, and Estimates, Prentice Hall PTR, 1986.
50 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.   DOI
51 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.   DOI
52 Fowler, M. and J. Highsmith. "The Agile Manifesto." Software Development 2001, 28-35.
53 Greene, W. H. Econometric Analysis. Upper Saddle River, New Jersey: Prentice Hall, 2000.
54 Hackman, J. R. and G. R. Oldham. "Work Redesign (Vol. 72)." Reading: Addison-Wesley, Vol. (1980).
55 Highsmith, J. "Agile Project Management: Principles and Tools." Cutter consortium, Vol. 4(2003), 1-37.
56 Highsmith, J. and A. Cockburn. "Agile Software Development: The Business of Innovation." Computer, Vol. 34, No. 9(2001), 120-27.   DOI
57 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.   DOI
58 Janzen, D. and H. Saiedian. "Test-Driven Development Concepts, Taxonomy, and Future Direction." Computer, Vol. 38, No. 9(2005), 43-50.   DOI
59 Kniberg, H. and M. Skarin. Kanban and Scrum-Making the Most of Both: Lulu.com, 2010.
60 Kanter, R. M. "Three Tiers for Innovation Research." Communication Research, Vol. 15, No. 5(1988), 509-23.   DOI
61 McCullagh, P. "Regression Models for Ordinal Data." Journal of the Royal Statistical Society: Series B (Methodological), Vol. 42, No. 2(1980), 109-27.   DOI
62 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.   DOI
63 Lindstrom, L. and R. Jeffries. "Extreme Programming and Agile Software Development Methodologies." Information systems management, Vol. 21, No. 3(2004), 41-52.   DOI
64 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.   DOI
65 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.   DOI
66 Morris, Peter WG, and George H. Hough. "The anatomy of major projects: A study of the reality of project management." (1987).
67 Phan, D., D. Vogel, and J. Nunamaker. "The Search for Perfect Project Management." Computerworld, Vol. 22, No. 39(1988), 95-100.
68 Myers, M. D. "Dialectical Hermeneutics: A Theoretical Framework for the Implementation of Information Systems." Information Systems Journal, Vol. 5, No. 1(1995), 51-70.   DOI
69 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.   DOI
70 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.   DOI