A DevOps collaboration culture acceptance model

Development and Operations (DevOps) is a buzzword in organisations developing software in which reacting to changing requirements and continuous delivery are inevitable. Resolving the issues of siloes between the development and operations departments in order to allow collaboration between them is the underlying philosophy of the DevOps movement. However, existing evidence indicates that the challenges surrounding the adoption of this collaboration culture by management and organisations may not necessarily translate to acceptance at implantation level by the teams. There is therefore a need for a model to guide the adoption. This study investigated human behavioural models and technology acceptance models that predict the behavioural intent to accept new technology. Based on the identified acceptance predictors, a model for successful acceptance of DevOps collaboration culture was proposed. This proposed model would be useful to software development organisations who have already adopted or are about to adopt DevOps.

[1]  Yee Yen Yuen,et al.  Internet Banking Adoption: Comparing Developed and Developing Countries , 2010, J. Comput. Inf. Syst..

[2]  Bill C. Hardgrave,et al.  Toward an information systems development acceptance model: the case of object-oriented systems development , 2003, IEEE Trans. Engineering Management.

[3]  Linda Ng Boyle,et al.  Extending the Technology Acceptance Model to assess automation , 2011, Cognition, Technology & Work.

[4]  Fred D. Davis,et al.  Investigating Determinants of Software Developers' Intentions to Follow Methodologies , 2003, J. Manag. Inf. Syst..

[5]  James Y. L. Thong,et al.  An Integrated Framework of Individual Acceptance of Agile Methodologies , 2007, PACIS.

[6]  Diane M. Strong,et al.  Extending the technology acceptance model with task-technology fit constructs , 1999, Inf. Manag..

[7]  Kenneth A. Kozar,et al.  Adopting Systems Development Methods: An Exploratory Study , 1989, J. Manag. Inf. Syst..

[8]  Frank Leymann,et al.  DevOpSlang - Bridging the Gap between Development and Operations , 2014, ESOCC.

[9]  Fred D. Davis.  Perceived Usefulness, Perceived Ease of Use, and User Acceptance of Information Technology , 1989, MIS Q..

[10]  A. Knabe.  Applying Ajzen's Theory of Planned Behavior to a Study of Online Course Adoption in Public Relations Education. , 2012 .

[11]  Michael Hüttermann.  DevOps for Developers , 2012, Apress.

[12]  Juhani Iivari,et al.  The relationship between organizational culture and the deployment of agile methods , 2011, Inf. Softw. Technol..

[13]  Deana R. Guardado.  Process acceptance and adoption by IT software project practitioners , 2012 .

[14]  Christoph Rosenkranz,et al.  The Role of Communication in Agile Systems Development , 2013, Bus. Inf. Syst. Eng..

[15]  Il Im,et al.  An international comparison of technology adoption: Testing the UTAUT model , 2011, Inf. Manag..

[16]  Jayantha Rajapakse,et al.  Extending the unified theory of acceptance and use of technology (UTAUT) model , 2011, The 4th International Conference on Interaction Sciences.

[17]  Megan Tschannen-Moran,et al.  A Multidisciplinary Analysis of the Nature, Meaning, and Measurement of Trust , 2000 .

[18]  Gordon B. Davis,et al.  User Acceptance of Information Technology: Toward a Unified View , 2003, MIS Q..

[19]  Elena Karahanna,et al.  Reconceptualizing Compatibility Beliefs , 2006 .

[20]  I. Ajzen,et al.  Belief, Attitude, Intention, and Behavior: An Introduction to Theory and Research , 1977 .

[21]  Younghwa Lee,et al.  The Technology Acceptance Model: Past, Present, and Future , 2003, Commun. Assoc. Inf. Syst..

[22]  V. Venkatesh,et al.  Unified Theory of Acceptance and Use of Technology: U.S. Vs. China , 2010 .

[23]  Fred D. Davis,et al.  A Theoretical Extension of the Technology Acceptance Model: Four Longitudinal Field Studies , 2000, Management Science.

[24]  Ritu Agarwal,et al.  A Conceptual and Operational Definition of Personal Innovativeness in the Domain of Information Technology , 1998, Inf. Syst. Res..

[25]  A. Carrón,et al.  Role Ambiguity, Task Cohesion, and Task Self-Efficacy , 2001 .

[26]  Mark R. Beauchamp,et al.  Role ambiguity, role efficacy, and role performance: Multidimensional and mediational relationships within interdependent sport teams. , 2002 .

[27]  Mahmoud Zouaoui,et al.  Organizational culture and the acceptance of agile methodology , 2016, 2016 International Conference on Digital Economy (ICDEc).

[28]  Fred D. Davis,et al.  A critical assessment of potential measurement biases in the technology acceptance model: three experiments , 1996, Int. J. Hum. Comput. Stud..

[29]  Elena Karahanna,et al.  Reconceptualizing Compatability Beliefs in Technology Acceptance Research , 2006, MIS Q..

[30]  O. Dijkstra,et al.  Extending the Agile Development Discipline to Deployment: The Need For a Holistic Approach , 2013 .

[31]  Fred D. Davis,et al.  Explaining Software Developer Acceptance of Methodologies: A Comparison of Five Theoretical Models , 2002, IEEE Trans. Software Eng..

[32]  Taysir M. Khatib.  Organizational culture, subcultures, and organizational commitment , 1996 .

[33]  Patrick Y. K. Chau,et al.  An empirical investigation on factors affecting the acceptance of CASE by systems developers , 1996, Inf. Manag..

[34]  Susan G. Straus,et al.  All in due time: The development of trust in computer-mediated and face-to-face teams , 2006 .

[35]  Viswanath Venkatesh,et al.  Unified Theory of Acceptance and Use of Technology: A Synthesis and the Road Ahead , 2016, J. Assoc. Inf. Syst..

[36]  Ivan Porres,et al.  DevOps: A Definition and Perceived Adoption Impediments , 2015, XP.

[37]  Thomas F. Stafford,et al.  Sources of conflict between developers and testers in software development , 2014, Inf. Manag..

[38]  A. Sohal,et al.  RESISTANCE: A CONSTRUCTIVE TOOL FOR CHANGE , 1998 .

[39]  Sven Laumer,et al.  Who influences whom? Analyzing workplace referents' social influence on IT adoption and non-adoption , 2009, J. Inf. Technol..

[40]  Dorothy Leonard-Barton,et al.  Implementing Structured Software Methodologies: A Case of Innovation in Process Technology , 1987 .

[41]  Viswanath Venkatesh,et al.  Technology Acceptance Model 3 and a Research Agenda on Interventions , 2008, Decis. Sci..

[42]  Moudy Elbayadi.  Relational Leadership, DevOps, and The Post-PC Era: Toward a Practical Theory for 21st Century Technology Leaders , 2014 .

[43]  Magda Huisman,et al.  Factors that affect the use and acceptance of systems development methodologies by system developers , 2004 .

[44]  Gwendolyn L. Kolfschoten,et al.  Trust Evolvement in Hybrid Team Collaboration: A Longitudinal Case Study , 2016 .

[45]  I. Ajzen.  The theory of planned behavior , 1991 .

[46]  Jijie Wang,et al.  Information technology (IT) in Saudi Arabia: Culture and the acceptance and use of IT , 2007, Inf. Manag..

[47]  N. Ellemers,et al.  Feeling Included and Valued: How Perceived Respect Affects Positive Team Identity and Willingness to Invest in the Team , 2013 .