Global Journal of Flexible Systems Management

, Volume 18, Issue 4, pp 275–289 | Cite as

Anti-patterns in Agile Adoption: A Grounded Theory Case Study of One Irish IT Organisation

Original Research


This paper presents a case study of one traditionally non-agile Information Technology (IT) services organisation in Ireland during its transition to implementing and using an agile development framework. The case study follows the experiences of using Scrum for a major IT systems conversion project in the insurance industry over the course of 9 months and 18 sprint cycles. A grounded theory approach was adopted to organically understand how productivity, effectiveness and workflow priorities emerged and were influenced by the agile approach. Secondary data sources, including the minutes of official track meetings and other stakeholder emails into the Scrum team, were analysed and categorised. A total of 460 work item requests were identified in the data, and a total of 88 work topic categories ultimately emerged from the grounded analysis. The 12 most repetitive topic categories, having demonstrated good data saturation, were subsequently selected for further analysis. The findings suggest that recurrent ad hoc requests from stakeholders into the Scrum development team significantly interrupted work on prioritised work items, making sprint objectives difficult to achieve and affecting Scrum team productivity and effectiveness overall. There was also broad evidence that powerful stakeholders tended to adhere to a traditional non-agile management philosophy, thus undermining the self-organising flexibility required by the agile approach. Stakeholders also often had no shared notion of when a work item or sprint goal was complete, thus contributing to the agile anti-patterns observed and suggesting that an agile culture had yet to emerge or instil within the traditionally non-agile organisation.


Agile Anti-patterns Case study Grounded theory Scrum 


  1. Ahimbisibwe, A., Cavana, R. Y., & Daellenbach, U. (2015). 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, 28(1), 7–33.CrossRefGoogle Scholar
  2. Annosi, M. C., Magnusson, M., Martini, A., & Appio, F. P. (2016). Social conduct, learning and innovation: An abductive study of the dark side of agile software development. Creativity and Innovation Management, 25(4), 515–535.CrossRefGoogle Scholar
  3. Badampudi, D., Fricker, S. A., & Moreno, A. M. (2013). Perspectives on productivity and delays in large-scale agile projects. In 14th international conference on agile software development, Vienna, Austria, 2013 (pp. 180–194): Springer.Google Scholar
  4. Baskerville, R., Pries-Heje, J., & Madsen, S. (2011). Post-agility: What follows a decade of agility? Information and Software Technology, 53(5), 543–555.CrossRefGoogle Scholar
  5. Carew, P. J., & Stapleton, L. (2014). Towards empathy: A human-centred analysis of rationality, ethics and praxis in systems development. AI & Society, 29(2), 149–166.CrossRefGoogle Scholar
  6. Cervone, H. F. (2011). Understanding agile project management methods using Scrum. OCLC Systems & Services: International Digital Library Perspectives, 27(1), 18–22.CrossRefGoogle Scholar
  7. Chandra Misra, S., Kumar, V., & Kumar, U. (2010). Identifying some critical changes required in adopting agile practices in traditional software development projects. International Journal of Quality & Reliability Management, 27(4), 451–474.CrossRefGoogle Scholar
  8. 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.CrossRefGoogle Scholar
  9. Conboy, K. (2009). Agility from first principles: Reconstructing the concept of agility in information systems development. Information Systems Research, 20(3), 329–354.CrossRefGoogle Scholar
  10. Conlon, P., & Carew, P. (2005). A risk driven framework for open source information systems development. In Proceedings of the 1st international conference on open source systems, Genova, Italy, 2005 (pp. 200–203).Google Scholar
  11. Cooke, J. L. (2014). Agile productivity unleashed: Proven approaches for achieving real productivity gains in any organization. Cambridgeshire: IT Governance Publishing.Google Scholar
  12. Cram, W. A. (2012). Aligning organizational values in systems development projects. Management Research Review, 35(8), 709–726.CrossRefGoogle Scholar
  13. Denning, S. (2016). Agile’s ten implementation challenges. Strategy & Leadership, 44(5), 15–20.CrossRefGoogle Scholar
  14. 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.CrossRefGoogle Scholar
  15. Dingsøyr, T., Nerur, S., Balijepally, V., & Moe, N. B. (2012). A decade of agile methodologies: Towards explaining agile software development. The Journal of Systems and Software, 6(85), 1213–1221.CrossRefGoogle Scholar
  16. Dorairaj, S., & Noble, J. (2013). Agile software development with distributed teams: Agility, distribution and trust. In Agile conference (AGILE), Nashville, TN, 2013 (pp. 1–10): IEEE.Google Scholar
  17. 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.CrossRefGoogle Scholar
  18. Dybå, T., & Dingsøyr, T. (2008). Empirical studies of agile software development: A systematic review. Information and Software Technology, 50(9), 833–859.CrossRefGoogle Scholar
  19. Eloranta, V.-P., Koskimies, K., & Mikkonen, T. (2016). Exploring ScrumBut—an empirical study of Scrum anti-patterns. Information and Software Technology, 74, 194–203.CrossRefGoogle Scholar
  20. Eloranta, V.-P., Koskimies, K., Mikkonen, T., & Vuorinen, J. (2013). Scrum anti-patterns—an empirical study. In 20th Asia-Pacific software engineering conference (APSEC), Bangkok, Thailand, 2013 (Vol. 1, pp. 503–510): IEEE.Google Scholar
  21. Fontana, A., & Frey, J. H. (2000). The interview: From structured questions to negotiated text. In N. K. Denzin & Y. S. Lincoln (Eds.), Handbook of qualitative research (pp. 645–672). CA: Sage.Google Scholar
  22. Fowler, M., & Highsmith, J. (2001). The agile manifesto. Software Development, 9(8), 28–35.Google Scholar
  23. Glaser, B. G. (1978). Theoretical sensitivity: Advances in the methodology of grounded theory. Mill Valley, CA: Sociology Press.Google Scholar
  24. Gregory, P., Barroca, L., Taylor, K., Salah, D., & Sharp, H. (2015). Agile challenges in practice: A thematic analysis. In 16th international conference on agile software development, Helsinki, Finland, 2015 (pp. 64–80): Springer.Google Scholar
  25. Hoda, R., Noble, J., & Marshall, S. (2011). The impact of inadequate customer collaboration on self-organizing Agile teams. Information and Software Technology, 53(5), 521–534.CrossRefGoogle Scholar
  26. Hoda, R., Noble, J., & Marshall, S. (2012). Developing a grounded theory to explain the practices of self-organizing Agile teams. Empirical Software Engineering, 17(6), 609–639.CrossRefGoogle Scholar
  27. Hummel, M. (2014). State-of-the-art: A systematic literature review on agile information systems development. In 47th Hawaii international conference on system sciences (HICSS), Waikoloa, HI, 2014 (pp. 4712–4721): IEEE.Google Scholar
  28. Hummel, M., Rosenkranz, C., & Holten, R. (2013). The role of communication in agile systems development. Business & Information Systems Engineering, 5(5), 343–355.CrossRefGoogle Scholar
  29. Iivari, J., & Iivari, N. (2011). The relationship between organizational culture and the deployment of agile methods. Information and Software Technology, 53(5), 509–520.CrossRefGoogle Scholar
  30. Inayat, I., Salim, S. S., Marczak, S., Daneva, M., & Shamshirband, S. (2015). A systematic literature review on agile requirements engineering practices and challenges. Computers in Human Behavior, 51, 915–929.CrossRefGoogle Scholar
  31. Kautz, K. (2011). Investigating the design process: participatory design in agile software development. Information Technology & People, 24(3), 217–235.CrossRefGoogle Scholar
  32. Loforte Ribeiro, F., & Timóteo Fernandes, M. (2010). Exploring agile methods in construction small and medium enterprises: A case study. Journal of Enterprise Information Management, 23(2), 161–180.CrossRefGoogle Scholar
  33. López-Martínez, J., Juárez-Ramírez, R., Huertas, C., Jiménez, S., & Guerra-García, C. (2016). Problems in the adoption of Agile-Scrum methodologies: A systematic literature review. In 4th international conference in software engineering research and innovation (CONISOFT), Puebla, Mexico, 2016 (pp. 141–148): IEEE.Google Scholar
  34. Murphy, B., Bird, C., Zimmermann, T., Williams, L., Nagappan, N., & Begel, A. (2013). Have agile techniques been the silver bullet for software development at microsoft? In ACM/IEEE 7th international symposium on empirical software engineering and measurement, Baltimore, MD, 2013 (pp. 75–84): IEEE.Google Scholar
  35. Schwaber, K., & Sutherland, J. (2012). Software in 30 days: How agile managers beat the odds, delight their customers, and leave competitors in the dust. New York, NY: Wiley.CrossRefGoogle Scholar
  36. Scrum Alliance (2015). The 2015 State of Scrum report. Scrum Alliance.Google Scholar
  37. Shastri, Y., Hoda, R., & Amor, R. (2017). Understanding the roles of the manager in agile project management. In Proceedings of the 10th innovations in software engineering conference, Jaipur, India, 2017 (pp. 45–55): ACM.Google Scholar
  38. Sommerville, I. (2015). Software engineering (10th ed.). Boston, MA: Addison-Wesley.Google Scholar
  39. Stankovic, D., Nikolic, V., Djordjevic, M., & Cao, D.-B. (2013). A survey study of critical success factors in agile software projects in former Yugoslavia IT companies. Journal of Systems and Software, 86(6), 1663–1678.CrossRefGoogle Scholar
  40. Stoica, M., Mircea, M., & Ghilic-Micu, B. (2013). Software development: Agile versus traditional. Informatica Economica, 17(4), 64.CrossRefGoogle Scholar
  41. Sushil, (2017). Flexible systems management as an iterative process. Global Journal of Flexible Systems Management, 18(2), 87–88.CrossRefGoogle Scholar
  42. Taylor, K. J. (2016). Adopting Agile software development: The project manager experience. Information Technology & People, 29(4), 670–687.CrossRefGoogle Scholar
  43. Walsham, G. (1993). Interpreting information systems in organizations. Chichester: Wiley.Google Scholar
  44. Yadav, V. (2016). A flexible management approach for globally distributed software projects. Global Journal of Flexible Systems Management, 17(1), 29–40.CrossRefGoogle Scholar
  45. Yin, R. K. (2013). Validity and generalization in future case study evaluations. Evaluation, 19(3), 321–332.CrossRefGoogle Scholar

Copyright information

© Global Institute of Flexible Systems Management 2017

Authors and Affiliations

  1. 1.INSYTE Centre for Information Systems and TechnocultureWaterford Institute of TechnologyWaterfordIreland

Personalised recommendations