A qualitative case study on agile practices and project success in agile software projects
Keywords:
Agile, practices, project success, success factors, project management, software projects, software teamsAbstract
In project management, and particularly software project management, there has been a shift from traditional plan based project management, to the agile event driven project management style. This paper identifies some of the most important agile practices a team should use, to succeed in an agile software project. Four participants in two different projects were interviewed. 53 often used practices were identified. 15 were found to be especially relevant in agile software projects. Six practices were related to quality, eight were related to scope and one was related to time. The results indicated that practices which improves customer feedback, helps the team to understand customer needs and improves the team process, are most likely to affect project success.
References
Agarwal, N., & Rathod, U. (2006). Defining ‘success’ for software projects: An exploratory revelation. International Journal of Project Management, 24(4), 358-370. doi:http://dx.doi.org/10.1016/j.ijproman.2005.11.009
Agile Alliance. Agile Manifesto. Retrieved from http://agilemanifesto.com
Alliance, A. (2015). Guide to agile practices. Retrieved from http://guide.agilealliance.org
Alliance, S. (2015). Scrum Guide. Retrieved from https://www.scrumalliance.org/why-scrum/scrum-guide
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. doi:http://dx.doi.org/10.1016/S0263-7863(98)00069-6
Beck, K., & Andres, C. (2004). Extreme Programming Explained: Embrace Change. Reading: Addison-Wesley Professional.
Boynton, A. C., & Zmud, R. W. (1984). An assessment of critical success factors. Sloan Management Review (pre-1986), 25(4), 17-27.
Bryde, D. J., & Robinson, L. (2005). Client versus contractor perspectives on project success criteria. International Journal of Project Management, 23(8), 622-629. doi:http://dx.doi.org/10.1016/j.ijproman.2005.05.003
Chappell, D. (2013). The Three Aspects of Software Quality: Functional, Structural, and Process. Retrieved from
Charette, R. (2005). Why software fails. IEEE Spectrum, 42, 42-49.
Chow, T., & Cao, D.-B. (2008). A survey study of critical success factors in agile software projects. The Journal of Systems and Software, 81(6), 961-971. doi:10.1016/j.jss.2007.08.020
Dybå, T., & Dingsøyr, T. (2008). Empirical studies of agile software development: A systematic review. Information and Software Technology, 50(9–10), 833-859. doi:http://dx.doi.org/10.1016/j.infsof.2008.01.006
Griffiths, M. (2012). PMI-ACP Exam Prep: RMC Publications, Inc.
Hammarberg, M., & Sundén, J. (2014). Kanban in Action: Manning Publications Co.
Jalali, S., & Wohlin, C. (2012). Global software engineering and agile practices: a systematic review. Journal of Software: Evolution and Process, 24(6), 643-659. doi:10.1002/smr.561
Lindvall, M., Basili, V., Boehm, B., Costa, P., Dangle, K., Shull, F., . . . Zelkowitz, M. (2002). Empirical Findings in Agile Methods. In D. Wells & L. Williams (Eds.), Extreme Programming and Agile Methods — XP/Agile Universe 2002 (Vol. 2418, pp. 197-207): Springer Berlin Heidelberg.
Mar, K., & Schwaber, K. (2002, March 22, 2002). Scrum with XP. informit.com.
Mens, T. (2008). Introduction and roadmap: History and challenges of software evolution: Springer.
Mistra, S. C., Kumar, V., & Kumar, U. (2009). Identifying some important success factors in adopting agile software development practices. The Journal of Systems and Software, 82(11), 1869-1890. doi:10.1016/j.jss.2009.05.052
Project Management Institute. (2013). A guide to the project management body of knowledge: (PMBOK guide). Newtown Square, Pa.: Project Management Institute.
Serrador, P., & Pinto, J. K. (2015). Does Agile work? — A quantitative analysis of agile project success. International Journal of Project Management, 33(5), 1040-1051. doi:http://dx.doi.org/10.1016/j.ijproman.2015.01.006
Siddique, L., & Hussein, B. A. (2016). A qualitative study of success criteria in Norwegian agile software projects from suppliers’ perspective. IJISPM-INTERNATIONAL JOURNAL OF INFORMATION SYSTEMS AND PROJECT MANAGEMENT, 4(2), 65-79.
The standish Group. (2015). CHAOS Report. Retrieved from
VersionOne. (2015). State of Agile Survey web page. Retrieved from http://stateofagile.versionone.com
VersionOne. (2016). 10th Annual State of Agile survey. Retrieved from
Wicks, A. M., & Roethlein, C. J. (2009). A Satisfaction-Based Definition of Quality. The Journal of Business and Economic Studies, 15(1), 82-97,110-111.
Williams, L., Brown, G., Meltzer, A., & Nagappan, N. (2011, 22-23 Sept. 2011). Scrum + Engineering Practices: Experiences of Three Microsoft Teams. Paper presented at the Empirical Software Engineering and Measurement (ESEM), 2011 International Symposium on.
Wysocki, R. K. (2014). Effective project management: traditional, agile, extreme. Indianapolis, Indiana: Wiley.
Yin, R. K. (1994). Case study research: design and methods (2nd ed.). Thousand Oaks, Calif.: Sage.
Yin, R. K. (2014). Case study research: design and methods (5th ed.). Thousand Oaks, Calif.: Sage.
Published
Issue
Section
License
Copyright (c) 2022 Andre Henriksen, Sven Arne R. Pedersen
This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.