Lessons from an Action Research Project

When an organization mindfully adopts an IT innovation there is a better chance that the innovation will meet the organization’s requirements (Swanson et al., 2004; Butler et al., 2006). Agile development principles (such as valuing individuals and interactions over processes and tools, and responding to change over following a plan) and practices (such as communicating frequently with users, and developing and releasing functionalities in short iterations) have the potential to increase organizational mindfulness during the development and adoption of an IT innovation. Action research in an organizational setting was used to study 1) the application of agile development principles and practices in developing an IT innovation and 2) whether the application of agile principles and practices could enable the organization to mindfully adopt that innovation. The lessons learned from the action research project are discussed using specific examples.

[1]  Ken Schwaber,et al.  Agile Project Management with Scrum , 1980 .

[2]  Richard O. Mason Lessons in Organizational Ethics from the Columbia Disaster: Can a Culture be Lethal? , 2004 .

[3]  Kent L. Beck,et al.  Extreme programming explained - embrace change , 1990 .

[4]  Nanda C. Surendra,et al.  Using an ethnographic process to conduct requirements analysis for agile systems development , 2008, Inf. Technol. Manag..

[5]  K. WeiK. The Collapse of Sensemaking in Organizations: The Mann Gulch Disaster , 2009, STUDI ORGANIZZATIVI.

[6]  Richard Baskerville,et al.  Special issue on action research in information systems: making is research relevant to practice--foreword , 2004 .

[7]  John M. Mulvey,et al.  Accountability and computer decision systems , 1995, CACM.

[8]  Martin Fowler,et al.  The new methodology , 2001, Wuhan University Journal of Natural Sciences.

[9]  Richard Baskerville,et al.  Investigating Information Systems with Action Research , 1999, Commun. Assoc. Inf. Syst..

[10]  Keng Siau,et al.  Agile Modeling, Agile Software Development, and Extreme Programming: The State of Research , 2005, J. Database Manag..

[11]  Kent L. Beck,et al.  Extreme programming explained - embrace change, Second Edition , 2005, The XP series.

[12]  Alistair Cockburn,et al.  Crystal Clear: A Human-Powered Methodology for Small Teams , 2004 .

[13]  Robert D. Galliers,et al.  The creation of 'best practice' software: Myth, reality and ethics , 2006, Inf. Organ..

[14]  Shane Warden,et al.  The art of agile development , 2007 .

[15]  Rajiv Kohli,et al.  Informating the Clan: Controlling Physicians' Costs and Outcomes , 2004, MIS Q..

[16]  William K. McHenry,et al.  The Russian's federation's Y2K policy: too little, too late? , 1999 .

[17]  Sue Newell,et al.  Exploring the Importance of Participation in the Post-Implementation Period of an ES Project: A Neglected Area , 2007, J. Assoc. Inf. Syst..

[18]  Jim Highsmith,et al.  Agile Software Development Ecosystems , 2002 .

[19]  Bernhard Rumpe,et al.  Assumptions Underlying Agile Software-Development Processes , 2005, J. Database Manag..

[20]  Brian S. Butler,et al.  Reliability, Mindfulness, and Information Systems , 2006, MIS Q..

[21]  E. Burton Swanson,et al.  Innovating Mindfully with Information Technology , 2004, MIS Q..

[22]  Kathleen M. Sutcliffe,et al.  Mindfulness and the Quality of Organizational Attention , 2006, Organ. Sci..

[23]  Agile Manifesto,et al.  Manifesto for Agile Software Development , 2001 .

[24]  David E. Avison,et al.  Controlling action research projects , 2001, Inf. Technol. People.

[25]  John A. Meacham,et al.  Wisdom and the Context of Knowledge: Knowing that One Doesn’t Know , 1983 .