Acceptance of software process innovations – the case of extreme programming
- 147 Downloads
Extreme programming (XP), arguably the most popular agile development methodology, is increasingly finding favor among software developers. Its adoption and acceptance require significant changes in work habits inculcated by traditional approaches that emphasize planning, prediction, and control. Given the growing interest in XP, it is surprising that there is a paucity of research articles that examine the factors that facilitate or hinder its adoption and eventual acceptance. This study aims to fill this void. Using a case study approach, we provide insights into individual, team, technological, task, and environmental factors that expedite or impede the organization-wide acceptance of XP. In particular, we study widely differing patterns of adherence to XP practices within an organization, and tease out the various issues and challenges posed by the adoption of XP. Based on our findings, we evolve factors and discuss their implications on the acceptance of XP practices.
Keywordsagile methodologies extreme programming (XP) organizational adoption of XP
The authors thank the editorial board of the special issue and the two anonymous reviewers for their constructive feedback and helpful suggestions during the review of this manuscript.
- Agile Alliance (2001) Agile manifesto. [WWW document] http://agilemanifesto.org (accessed 26 February 2009).
- Ambler S (2007) Survey says … Agile has crossed the chasm. Dr. Dobb’′s Journal 32 (8) [WWW document] http://www.ddj.com/architect/200001986 (accessed 7 July 2009).
- Beck K (2000) Extreme Programming Explained: Embrace Change. Addison-Wesley, Reading, MA.Google Scholar
- Beck K and Andres C (2005) Extreme Programming Explained: Embrace Change. Addison-Wesley, Boston, MA.Google Scholar
- Boehm BW and Turner R (2004) Balancing Agility and Discipline: A Guide for the Perplexed. Addison-Wesley, Boston, MA.Google Scholar
- Cao L, Mohan K, Xu P and Ramesh B (2004) How extreme does extreme programming have to be? Adapting XP practices to large-scale projects. In Proceedings of the 37th Hawaii International Conference on System Sciences (Sprague, RH, Ed.), IEEE, Hawaii.Google Scholar
- Cho H and Kim YG (2001) Critical factors for assimilation of object-oriented programming languages. Journal of Management Information Systems 18 (3), 125–156.Google Scholar
- Cockburn A (2002) Agile Software Development. Addison-Wesley, Boston, MA.Google Scholar
- Conboy K, Pikkarainen M and Wang X (2007) Agile practices in use from an innovation assimilation perspective: a multiple case study. In Twenty Eighth International Conference on Information Systems. (Rivard S and Webster J, Eds.), Montreal, Canada.Google Scholar
- Eisenhardt KM (1989) Building theories from case-study research. Academy of Management Review 14 (4), 532–550.Google Scholar
- Fruhling A, Mcdonald P and Dunbar C (2008) A case study: introducing extreme programming in a US government system development project. In Proceedings of the 41st Hawaii International Conference on System Sciences. (Sprague RH, Ed.), IEEE, Hawaii.Google Scholar
- Hardgrave B, Davis F and Riemenschneider C (2003) Investigating determinants of software developers’ intentions to follow methodologies. Journal of Management Information Systems 20 (1), 123–151.Google Scholar
- Highsmith J (2003) Agile project management: principles and tools. Cutter Consortium Reports, Cutter Consortium, Arlington, MA.Google Scholar
- Highsmith JA (2002) Agile Software Development Ecosystems. Addison-Wesley, Boston.Google Scholar
- Jasperson JS, Carter PE and Zmud RW (2005) A comprehensive conceptualization of post-adoptive behaviors associated with information technology enabled work systems. MIS Quarterly 29 (3), 525–557.Google Scholar
- Jeffries R (2001) What is extreme programming? [WWW document] http://www.xprogramming.com/xpmag/whatisxp.htm (accessed 26 February 2009).
- Kwon TH and Zmud RW (1987) Unifying the fragmented models of information systems implementation. In Critical Issues in Information Systems Research (BOLAND RJ and HIRSCHHEIM RA, Eds), pp 227–251, John Wiley & Sons Ltd., New York, NY.Google Scholar
- Riemenschneider CK and Hardgrave BC (2001) Explaining software development tool use with the technology acceptance model. Journal of Computer Information Systems 41 (4), 1–8.Google Scholar
- Salo O (2004) Improving software process in agile software development projects: results from two XP case studies. In Proceedings of the 30th EUROMICRO Conference. (Steinmetz R and Mauthe A, Eds.), IEEE, Rennes, France.Google Scholar
- Sarker S, Valacich J and Sarker S (2005) Technology adoption by groups: a valance perspective. Journal of Association for Information Systems 6 (2), 37–71.Google Scholar
- Shtub A, Bard JF and Globerson S (2005) Project Management: Processes, Methodologies, and Economics. Pearson Prentice Hall, Upper Saddle River, NJ.Google Scholar
- Yin RK (1994) Case Study Research: Design and Methods. Sage Publications, Thousand Oaks, CA.Google Scholar