A Failure to Learn By Software Developers: Inhibiting the Adoption of an Agile Software Development Methodology

Reference

• Acuna, S., & Juisto, N. (2004). Assigning people to roles in software projects Software: Practice and experience, 34 (7), 675–696.
   Web of Science ®Google Scholar
• Argyris, C. (1976). Single-loop and double-loop models in research on decision making. Administrative Science Quarterly, 21 (3), 363–375.
   Web of Science ®Google Scholar
• Argyris, C. (1994). Good communication that blocks learning. Harvard Business Review, 72 (4), 77–85.
   Web of Science ®Google Scholar
• Argyris, C. (1995). Action science and organizational learning. Journal of Managerial Psychology, 10 (6), 20–26.
   Google Scholar
• Argyris, C. (1997). Double loop learning in organizations. Harvard Business Review, 55 (5), 115–125. 6. Argyris, C. (2002). Double loop learning, teaching, and research. Academy of Management Learning and Education, 1 (2), 206–218.
   Google Scholar
• Argyris, C., & Schon, D. (1978). Organizational learning: A theory of action perspective. MA, USA: Addison-Wesley.
   Google Scholar
• Astels, D., Miller, G. and Movak, M. (2002) A practical guide to extreme programming. NJ, USA: Prentice Hall.
   Google Scholar
• Attride-Sterling, J. (2001). Thematic networks: an analytical tool for qualitative research. Qualitative Research, 1 (3), 385–405.
   Google Scholar
• Augustine, S. (2005). Managing Agile Projects. IA, USA: Prentice Hall.
   Google Scholar
• Back, K., & Seaker, R. (2004). Project performance: Implications of personality preferences and double loop learning. Journal of American Academy of Business, 4 (1), 292–297.
   Google Scholar
• Badawy, M. (1997). The role of the technical manager, In R. Katz (Ed.), The human side of managing technological innovation (229–236). NY, USA: Oxford University Press.
   Google Scholar
• Beck, K. (2000). Extreme programming explained. Embrace change. NY, USA: Addison Wesley.
   Google Scholar
• Blackman, D., Connelly, J., & Henderson, S. (2004). Does double loop learning create reliable knowledge? The Learning Organization, 11 (1), 11–27.
   Google Scholar
• Bodker, K., & Pedersen, J. (1991). Workplace cultures: Looking at artifacts, symbols and practices, In K. Greenbaum & M. Kyng (Eds.), Design at Work: Cooperative Design of Computer Systems (121–136). NJ, USA: Lawrence Erlbaum Associates.
   Google Scholar
• Boehm, B., & Turner, R. (2004). Balancing agility and discipline: Pearson Education, MA, USA.
   Google Scholar
• Bokeno, R. (2003). The work of Chris Argyris as critical organization practice. Journal of Organizational Change Management, 16 (6), 633–649.
   Web of Science ®Google Scholar
• Boody, D., & Buchanan, D. (1992). Take the lead. Interpersonal skills for project managers. Hertfordshire, UK: Prentice Hall.
   Google Scholar
• Bossavit, L. (2002). The unbearable lightness of programming: A tale of two cultures. Cutter IT Journal, 15 (9), 5–11.
   Google Scholar
• Brehm, J., & Cohen, A. (1962). Explorations in cognitive dissonance. NY, USA: John Wiley & Sons.
   Google Scholar
• Capretz, L. (2002). Are software engineers really engineers. World Transactions on Engineering and Technology Education, 1 (2), 233–235.
   Google Scholar
• Carmel, E., & Sawyer, S. (1998). Packaged software development teams: What makes them different. Information Technology and People, 11 (1), 7–19.
   Google Scholar
• Coffee, P. (2001). No more excuses: Innovation technology and irrelevant tangents. In L. Constantine (Ed.), Beyond chaos: The expert edge in managing software development. NJ, USA: Addison-Wesley.
   Google Scholar
• Cooper, A. (2004). The inmates are running the asylum. IN, USA: Sams Publishing.
   Google Scholar
• Coram, M., & Bohner, S. (2005). The impact of agile methods on software project management. Paper presented at the IEEE International Conference on the Engineering of Computer-Based Systems, Greenbelt, MD, USA.
   Google Scholar
• Couger, J., & McIntyre, S. (1988). Motivation norms of knowledge engineers compared to those of software engineers. Journal of Management Information Systems, 4 (3), 82–93.
   Google Scholar
• Couger, J., Zawacki, R., & Oppermann, E. (1979). Motivation levels of MIS managers versus those of their employees. MIS Quarterly, 3 (3), 47–56.
   Web of Science ®Google Scholar
• Curtis, B., Krasner, H., & Iscoe, N. (1988). A field study of the software design process for large systems. Communications of the ACM, 31 (11), 1268–1287.
   Web of Science ®Google Scholar
• Denhardt, R., Denhardt, J., & Aristigeuta, M. (2002). Managing behavior in public and nonprofit organizations. CA, USA: Sage Publications.
   Google Scholar
• Drobka, J., Noftz, D., & Raghu, R. (2004). Piloting XP on four mission-critical projects. IEEE Software, 21 (6), 70–75.
   Web of Science ®Google Scholar
• Easterby-Smith, M., & Lyles, M. (2003). Re-reading organizational learning: Selective memory, forgetting, and adaptation. Academy of Management Executive, 17 (2), 51–55.
   Google Scholar
• Ezey, P. (2003). Integration and its challenges in participant observation. Qualitative Research, 3 (2), 191–205.
   Google Scholar
• Fitzgerald, B. (1997). The use of systems development methodologies in practice: a field study. Information Systems Journal, 7 (3), 210–212.
   Web of Science ®Google Scholar
• Furumo, K., & Melcher, A. (2006). The importance of social structure in implementing ERP systems: A case study using Adaptive Structuration theory. Journal of Information Technology Case and Application Research, 8 (2), 39–58.
   Google Scholar
• Goleman, D. (1996). Vital Lies Simple Truths: The Psychology of Self-Deception. NY, USA: Simon and Schuster Books.
   Google Scholar
• Gordon, S. (2008). The case for case-based research. Journal of Information Technology Case and Application Research, 10 (1), 1–6.
   Google Scholar
• Greenwald, A., & Ronis, D. (1978). Twenty years of cognitive dissonance: Case study of the evolution of a theory. Psychological Review, 85 (1), 53–57.
   PubMed Web of Science ®Google Scholar
• Grossman, F., Bergin, J., Leip, D., Merrit, S., & Gotel, O. (2004). One XP experience: introducing agile (XP) software development into a culture that is willing but not ready. Paper presented at the Conference of the Centre for Advanced Studies on Collaborative research Ontaario, Canada.
   Google Scholar
• Hazzan, O., & Tomayko, J. (2003). The reflective practitioner perspective in extreme programming. Paper presented at the Extreme programming and agile methods - Xp/Agile universe 2003, New Orleans.
   Google Scholar
• Highsmith, J. (2004). Agile project management. MA, USA: Pearson Education.
   Google Scholar
• Hodgetts, P. (2004). Refactoring the development process: Experiences with the incremental adoption of Agile practices, Paper presented at the Agile Development Conference (ADC04) Salt Lake City.
   Google Scholar
• Howard, A. (2001). On site: Software engineering project management. Communications of the ACM 44 (5), 23–24.
   Web of Science ®Google Scholar
• Humphrey, W. (1996). Making software manageable. Crosstalk, 9 (12), 3–6.
   Google Scholar
• Hunt, A., & Thomas, D. (2000). The pragmatic programmer. MA, USA: Addison Wesley Longman.
   Google Scholar
• Hunt, A., & Thomas, D. (2002). Software archaeology. IEEE Software, 19 (2), 20–22.
   Web of Science ®Google Scholar
• Jones, M., & McLean, E. (1970). Management problems in large-scale software development projects. Industrial Management Review, 11 (3), 1–16.
   Google Scholar
• Jorgensen, D. (1989). Participant observation: A methodology for human studies. CA, USA: Sage Publications.
   Google Scholar
• Joshi, K. (2005). Understanding user resistance and acceptance during the Implementation of an order management system: A case study using the equity implementation model. Journal of Information Technology Case and Application Research, 7 (1), 6–20.
   Google Scholar
• Kahkonen, T., & Abrahamsson, P. (2003). Digging into the fundamentals of extreme programming building the theoretical base for agile methods, Paper presented at the 29th Euromicro Conference, Antalya, Turkey.
   Google Scholar
• Kitchenham, B., Pickard, L., & Pfleeger, S. (1995) Case studies for method and tool evaluation. IEEE Software, 12 (4), 52–62.
   Web of Science ®Google Scholar
• Klein, K., & Myers, M. (1999). A Set of Principles for Conducting and Evaluating Interpretive Field Studies in Information Systems. MIS Quarterly, 23 (1), 67–94.
   Web of Science ®Google Scholar
• Koutsoukos, G. (2006). Mentality patterns: Capturing and dealing explicitly with recurring turns of mind in software development, Paper presented at the 13th European Conference EuroSPI, Joensuu, Finland.
   Google Scholar
• Larsen, T. (2001). The phenomenon of diffusion, In M. Ardis & B. Marcolin (Eds.), Diffusing software product and process innovations (35–50). MA, USA: Kluwer Academic Publishers.
   Google Scholar
• Layman, L., Williams, L., & Cunningham, L. (2004). Exploring extreme programming in context: an industrial case study, Paper presented at the Agile Development Conference (ADC04), Salt Lake City.
   Google Scholar
• Layman, L., Williams, L., & Cunningham, L. (2006). Motivations and measurements in an agile case study. Journal of Systems Architecture, 52 (11), 654–667.
   Web of Science ®Google Scholar
• Licker, P. (1983). The Japanese Approach: A Better Way To Manage Programmers. Communications of the ACM, 26 (9), 631–636.
   Web of Science ®Google Scholar
• Licker, P. (1985). The Art of Managing Software Development People. NY, USA: John Wiley & Sons.
   Google Scholar
• Lindstrom, L., & Jeffries, R. (2004). Extreme Programming and Agile software development methodologies. Information Systems Management, 21 (3), 41–52.
   Web of Science ®Google Scholar
• Maurer, F., & Martel, S. (2002). Extreme Programming: Rapid Development for Web-Based Applications. IEEE Internet Computing, 6 (1), 86–90.
   Web of Science ®Google Scholar
• McAvoy, J., & Butler, T. (2007) A failure to learn in a software development team: The unsuccessful introduction of an Agile method Paper presented at the 16th International Conference on Information Systems Development Galway, Ireland.
   Google Scholar
• Molla, A., & Bhalla, A. (2006). Business transformation through ERP: A case study of an Asian company. Journal of Information Technology Case and Application Research, 8 (1), 34–54.
   Google Scholar
• Natsu, H., Favela, J., Morán, A., Decouchant, D., & Martinez-Enriquez, A. (2003). Distributed Pair Programming on the Web Paper presented at the 4th Mexican International Conference on Computer Science Tlaxcala, Mexico.
   Google Scholar
• Olson, D., & Stimmel, C. (2002). The manager pool. Patterns for radical leadership: Addison-Wesley. NJ, USA.
   Google Scholar
• Poole, C. (2004) Distributed product development using extreme programming Paper presented at the Extreme programming and agile processes in software engineering 5th International Conference Garmisch-Partenkirchen, Germany.
   Google Scholar
• Raymond, E. (1999). The cathedral and the bazaar. CA, USA: O’Reilly & Associates.
   Google Scholar
• Riehle, D. (2001). A comparison of the value systems of Adaptive Software Development and Extreme Programming: How methodologies may learn from each other, In G. Succi & M. Marchesi (Eds.), Extreme Programming explained (35–50). Boston, USA: Addison-Wesley.
   Google Scholar
• Robinson, H., & Sharp, H. (2005). The social side of technical practices, Paper presented at the 6th International Conference on Extreme Programming and Agile processes in software engineering (XP2005), Sheffield, UK.
   Google Scholar
• Rumpe, B., & Schroeder, A. (2002). Quantitative survey on Extreme Programming projects, Paper presented at the International Conference on Extreme Programming and Flexible Processes in Software Engineering (XP2002), Alghero, Italy.
   Google Scholar
• Salaway, G. (1987). An organizational learning approach to information systems development. MIS Quarterly, 11 (2), 245–264.
   Web of Science ®Google Scholar
• Sawyer, S., & Guinan, P. (1998). Software development: Processes and performance. IBM Systems Journal, 37 (4), 552–569.
   Google Scholar
• Schuh, P. (2001). Recovery, Redemption, and Extreme Programming. IEEE Software, 18 (6), 34–41.
   Web of Science ®Google Scholar
• Schuh, P. (2004) Integrating agile development in the real world. NY, USA: Delmar Thomson Learning
   Google Scholar
• Schwaber, K. (2002). When and where Agile suceeds. Cutter IT Journal, 15 (9), 22–27.
   Google Scholar
• Seaman, C. (1999). Qualitative methods in emperical studies of software engineering. IEEE Transactions on Software Engineering, 25 (4), 557–572.
   Web of Science ®Google Scholar
• Simons, M., & Nadkarny, C. (2002). Extreme India. Cutter IT Journal, 15 (9), 28–33.
   Google Scholar
• Spayd, M. (2003). Evolving agile in the enterprise: implementing XP on a grand scale. Paper presented at the Agile Development Conference, Salt Lake City, Utah.
   Google Scholar
• Stake, R. (1995). The art of case study research. CA, USA: Sage Publications.
   Google Scholar
• Stephens, M., & Rosenberg, D. (2003). Extreme Programming refactored: The case against XP. Heidleberg, Germany: Springer-Verlag.
   Google Scholar
• Turk, D., France, R., & Rumpe, B. (2005). Assumptions underlying Agile software development processes. Journal of Database Management, 16 (4), 62–87.
   Web of Science ®Google Scholar
• Von Bergen, C., & Kirk, R. (1978) Groupthink: When too many heads spoil the decision, Management Review, 67 (3), 44–49.
   PubMedGoogle Scholar
• Vroom, V. (1974) A normative model of managerial decision-making, In Pugh, D (Ed.), Organization theory. Third Edition (309–328). London, UK: Penguin Books.
   Google Scholar
• Walsham, G. (1995). Interpretive Case Studies in IS Research: Nature and Method. European Journal of Information Systems, 4 (1), 74–81.
   Web of Science ®Google Scholar
• Weinberg, G. (1971). The psychology of computer programming. NY, USA: Van Nostrand Reinhold Co.
   Google Scholar
• Wendorff, P. (2002). Organisational Culture in Agile Software Development, Paper presented at the Product Focused Software Process Improvement : 14th International Conference, PROFES 2002, Rovaniemi, Finland.
   Google Scholar
• Wiegers, K. (2001). First things first: A project managers primer, In L. Constantine (Ed.), Beyond chaos: The expert edge in managing software development (49–55). NJ, USA: Addison-Wesley.
   Google Scholar
• Workman, J. (1997). Engineers’ interactions with marketing groups in an engineering-driven organization, In R. Katz (Ed.), The human side of managing technological innovation (535–549). NY, USA: Oxford University Press.
   Google Scholar
• Yin, R. (2003). Case Study Research: Design and Method. CA, USA: Sage Publications.
   Google Scholar
• Yourdon, E. (1993). Decline and fall of the American programmer. NJ, USA: Prentice Hall Inc.
   Google Scholar