Advertisement

Barriers to Learning in Agile Software Development Projects

  • Jeffry S. Babb
  • Rashina Hoda
  • Jacob Nørbjerg
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 149)

Abstract

The adoption of agile methods promises many advantages for individual, team, and organizational learning. However, environmental, structural, and organizational/cultural constraints often find teams adapting agile software development methods rather than engaging in full adoption. We present results from two qualitative studies of teams and organizations that have, in many cases, adapted agile software methods to suit their needs through the omission or alteration of aspects of the method. In many cases, aspects of an agile method that are most related to learning were those that were modified or omitted. This paper utilizes the results of these studies to identify common and emergent barriers to learning. Often these barriers to learning exist according to organizational culture and the extent to which that culture influences attitudes, norms, and behaviors pertaining to learning. We present these barriers to learning and provide insight to the causes, effects, and potential ameliorations for these barriers.

Keywords

Agile software development learning organizational culture XP Scrum Dialogical Action Research Grounded Theory 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Argyris, C., Schön, D.: Organizational Learning II – Theory, Method, and Practice. Addison-Wesley, Boston (1996)Google Scholar
  2. 2.
    Babb, J.J.: Towards a reflective-agile learning model and method in the case of small shop software development: evidence from an action research study. PhD., Virginia Commonwealth University (2009)Google Scholar
  3. 3.
    Babb, J.J., Nørbjerg, J.: A Model for Reflective Learning in Small Shop Agile Development. In: Molka-Danielsen, J., Nicolajsen, H.W., Persson, J.S. (eds.) Engaged Scandinavian Research. Selected Papers of the Information Systems Research Seminar in Scandinavia, Molde, Norway, vol. 1, pp. 23–38. Tapir Akademisk Forlag (2010)Google Scholar
  4. 4.
    Bansler, J.P., Bødker, K.: A Reappraisal of Structured Analysis: Design in an Organiza-tional Context. ACM Transactions on Information Systems 11(2), 165–193 (1993)CrossRefGoogle Scholar
  5. 5.
    Boehm, B., Turner, R.: Balancing Agility and Discipline: A Guide for the Perplexed. Addison-Wesley, Boston (2004)Google Scholar
  6. 6.
    Beck, K.: Extreme Programming Explained. Addison-Wesley, Boston (2000)Google Scholar
  7. 7.
    Cao, L., Mohan, K., Xu, P., Ramesh, B.: A framework for adapting agile development methodologies. European Journal of Information Systems 18, 332–343 (2009)CrossRefGoogle Scholar
  8. 8.
    Chau, T., Maurer, F., Melnik, G.: Knowledge Sharing: Agile Methods vs. Tayloristic Methods. In: Twelfth IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises, WETICE 2003. IEEE Computer Society (2003)Google Scholar
  9. 9.
    Cockburn, A.: Agile Software Development. Addison-Wesley, Boston (2002)Google Scholar
  10. 10.
    Coleman, G., O’Connor, R.: Investigating software process in practice: A grounded theory perspective. J. Syst. Softw. 81(5), 772–784 (2008)CrossRefGoogle Scholar
  11. 11.
    Fitzgerald, B., Russo, N.L., Stolterman, E.: Information Systems Development. Methods in Action. McGraw-Hill (2002)Google Scholar
  12. 12.
    Glaser, B., Strauss, A.L.: The Discovery of Grounded Theory. Aldine, Chicago (1967)Google Scholar
  13. 13.
    Guindon, R.: Designing the Design Process: Exploiting Opportunistic Thoughts. Human-Computer Interaction 5, 305–344 (1990)CrossRefGoogle Scholar
  14. 14.
    Guindon, R.: Knowledge exploited by experts during software systems design. International Journal of Man-Machine Studies 33, 279–304 (1990)CrossRefGoogle Scholar
  15. 15.
    Hazzan, O., Tomayko, J.: The Reflective Practitioner Perspective in eXtreme Programming. In: Maurer, F., Wells, D. (eds.) XP/Agile Universe 2003. LNCS, vol. 2753, pp. 51–61. Springer, Heidelberg (2003)CrossRefGoogle Scholar
  16. 16.
    Hoda, R., Kruchten, P., Noble, J., Marshall, J.: Agility in Context. In: Object-Oriented Programming, Systmes, Languages and Applications Conference, OOPSLA 2010, Reno/Tahoe, NV. ACM (2010)Google Scholar
  17. 17.
    Hoda, R., Noble, J., Marshall, S.: Agile Undercover: When Customers Don’t Collaborate. In: Sillitti, A., Martin, A., Wang, X., Whitworth, E. (eds.) XP 2010. LNBIP, vol. 48, pp. 73–87. Springer, Heidelberg (2010)CrossRefGoogle Scholar
  18. 18.
    Holz, H., Maurer, F.: Knowledge Management Support for Distributed Agile Software Processes. In: Henninger, S., Maurer, F. (eds.) LSO 2003. LNCS, vol. 2640, pp. 60–80. Springer, Heidelberg (2003)CrossRefGoogle Scholar
  19. 19.
    Humphrey, W.S.: Managing the Software Process. Addison-Wesley, Reading (1990)Google Scholar
  20. 20.
    Kautz, K., Madsen, S., Nørbjerg, J.: Persistent Problems and Practices in Information Systems Development. ISJ (2007) (accepted for publication)Google Scholar
  21. 21.
    Lee, A.S., Mårtensson, P.: Dialogical Action Research at Omega Corporation, Richmond, VA, pp. 1–39 (2004)Google Scholar
  22. 22.
    Madsen, S., Kautz, K., Vidgen, R.: A framework for understanding how a unique and local IS development method emerges in practice. European Journal of Information Systems 15, 225–238 (2006)CrossRefGoogle Scholar
  23. 23.
    Mangalaraj, G., Mahapatra, R., Nerur, S.: Acceptance of software process innovations – the case of extreme programming. European Journal of Information Systems 18, 344–354 (2009)CrossRefGoogle Scholar
  24. 24.
    Mathiassen, L., Pries-Heje, J., Ngwenyama, O. (eds.): Improving Software Organizations. From Principles to Practice, The Agile Software Development Series. Addison-Wesley, Boston (2002)Google Scholar
  25. 25.
    Melnik, G., Maurer, F.: Direct Verbal Communication as a Catalyst of Agile Knowledge Sharing. In: Agile Development Conference (ADC 2004). IEEE Computer Society (2004)Google Scholar
  26. 26.
    Moe, N.B., Dingsøyr, T., Dybå, T.: A teamwork model for understanding an agile team: A case study of a Scrum project. Information and Software Technology 52, 480–491 (2010)CrossRefGoogle Scholar
  27. 27.
    Nerur, S., Balijepally, V.: Theoretical Reflections on Agile Development Methodologies. Commun. ACM 50(3), 79–83 (2007)CrossRefGoogle Scholar
  28. 28.
    Rubin, K.S.: Essential Scrum: A Practical Guide to the Most Popular Agile Process. Addison-Wesley, Boston (2013)Google Scholar
  29. 29.
    Schein, E.H.: Oraganizational Culture and Leadership, 1st edn. Jossey-Bass Publishers, San Franciso (1985)Google Scholar
  30. 30.
    Schön, D.A.: The Reflective Practitioner. How Professionals Think in Action. Basic Books (1983)Google Scholar
  31. 31.
    Schön, D.A.: Designing as reflective conversation with the materials of a design situation. Knowledge-Based Systems 5(1), 3–13 (1992)CrossRefGoogle Scholar
  32. 32.
    Senapathi, M., Srinivasan, A.: Understanding post-adoptive agile usage: An exploratory cross-case analysis. The Journal of Systems and Software 85, 1255–1268 (2012)CrossRefGoogle Scholar
  33. 33.
    Steiner, L.: Organizational dilemmas as barriers to learning. The Learning Organization 5(4), 193–201 (1998)CrossRefGoogle Scholar
  34. 34.
    Stolterman, E.: How System Designers Think about Design and Methods. Some Reflections Based on an Interview Study. Scandinavian Journal of Information Systems 3, 137 (1991)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2013

Authors and Affiliations

  • Jeffry S. Babb
    • 1
  • Rashina Hoda
    • 2
  • Jacob Nørbjerg
    • 3
  1. 1.Department of Computer Information and Decision ManagementWest Texas A&M UniversityCanyonUSA
  2. 2.Electrical and Computer EngineeringThe University of AucklandAucklandNew Zealand
  3. 3.Department of IT ManagementCopenhagen Business SchoolFrederiksbergDenmark

Personalised recommendations