DevOps Team Structures: Characterization and Implications

Context: DevOps can be defined as a cultural movement to improve and accelerate the delivery of business value by making the collaboration between development and operations effective. Objective: This paper aims to help practitioners and researchers to better understand the organizational structure and characteristics of teams adopting DevOps. Method: We conducted an exploratory study by leveraging in depth, semi-structured interviews to relevant stakeholders of 31 multinational software-intensive companies, together with industrial workshops and observations at organizations’ facilities that supported triangulation. We used Grounded Theory as qualitative research method to explore the structure and characteristics of teams, and statistical analysis to discover their implications in software delivery performance. Results: We describe a taxonomy of team structure patterns that shows emerging, stable and consolidated product teams that are classified according to six variables, such as collaboration frequency, product ownership sharing, autonomy, among others, as well as their implications on software delivery performance. These teams are often supported by horizontal teams (DevOps platform teams, Centers of Excellence, and chapters) that provide them with platform technical capability, mentoring and evangelization, and even temporarily facilitate human resources. Conclusion: This study aims to strengthen evidence and support practitioners in making better informed about organizational team structures by analyzing their main characteristics and implications in software delivery performance.

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

[2]  Pasi Kuvaja,et al.  An Exploratory Study of DevOps Extending the Dimensions of DevOps with Practices , 2016 .

[3]  Ivan Porres,et al.  On the Impact of Mixing Responsibilities Between Devs and Ops , 2016, XP.

[4]  Paul Ralph,et al.  Toward Methodological Guidelines for Process Theories and Taxonomies in Software Engineering , 2019, IEEE Transactions on Software Engineering.

[5]  Fabio Kon,et al.  Building a Theory of Software Teams Organization in a Continuous Delivery Context , 2020, 2020 IEEE/ACM 42nd International Conference on Software Engineering: Companion Proceedings (ICSE-Companion).

[6]  Tomi Männistö,et al.  DevOps Adoption Benefits and Challenges in Practice: A Case Study , 2016, PROFES.

[7]  A. Strauss,et al.  The discovery of grounded theory: strategies for qualitative research aldine de gruyter , 1968 .

[8]  Rodrigo Bonifácio,et al.  Adopting DevOps in the real world: A theory, a model, and a case study , 2019, J. Syst. Softw..

[9]  Tore Dybå,et al.  Building Theories in Software Engineering , 2008, Guide to Advanced Empirical Software Engineering.

[10]  Paul Ralph,et al.  Grounded Theory in Software Engineering Research: A Critical Review and Guidelines , 2016, 2016 IEEE/ACM 38th International Conference on Software Engineering (ICSE).

[11]  Liming Zhu,et al.  Adopting Continuous Delivery and Deployment: Impacts on Team Structures, Collaboration and Responsibilities , 2017, EASE.

[12]  Andrea Villegas,et al.  DevOps in Practice - A preliminary Analysis of two Multinational Companies , 2019, PROFES.

[13]  Magnus C. Ohlsson,et al.  Experimentation in Software Engineering , 2000, The Kluwer International Series in Software Engineering.

[14]  Tullio Vardanega,et al.  DevOps Meets Dynamic Orchestration , 2018, DEVOPS.

[15]  Pasi Kuvaja,et al.  Relationship of DevOps to Agile, Lean and Continuous Deployment - A Multivocal Literature Review Study , 2016, PROFES.

[16]  Alexander Scheerer,et al.  Coordination Challenges in Large-Scale Software Development: A Case Study of Planning Misalignment in Hybrid Settings , 2018, IEEE Transactions on Software Engineering.

[17]  Bjørnar Tessem,et al.  Problems in the interplay of development and IT operations in system development projects: A Delphi study of Norwegian IT experts , 2011, Inf. Softw. Technol..

[18]  Daniela Cruzes,et al.  Recommended Steps for Thematic Synthesis in Software Engineering , 2011, 2011 International Symposium on Empirical Software Engineering and Measurement.

[19]  Bertrand Meyer,et al.  Software Engineering Aspects of Continuous Development and New Paradigms of Software Production and Deployment , 2018, Lecture Notes in Computer Science.

[20]  Maya Daneva,et al.  A Mapping Study on Cooperation between Information System Development and Operations , 2014, PROFES.

[21]  Janice Singer,et al.  Studying Software Engineers: Data Collection Techniques for Software Field Studies , 2005, Empirical Software Engineering.

[22]  Mohanad Halaweh,et al.  Integrating the Grounded Theory Method and Case Study Research Methodology Within IS Research: A Possible 'Road Map' , 2008, ICIS.

[23]  John Grundy,et al.  Recruitment, engagement and feedback in empirical software engineering studies in industrial contexts , 2017, Inf. Softw. Technol..

[24]  Daniela E. Damian,et al.  Selecting Empirical Methods for Software Engineering Research , 2008, Guide to Advanced Empirical Software Engineering.

[25]  Miguel P Caldas,et al.  Research design: qualitative, quantitative, and mixed methods approaches , 2003 .

[26]  Fabio Kon,et al.  Platform Teams: An Organizational Structure for Continuous Delivery , 2020, ICSE.

[27]  Jim Buchan,et al.  DevOps Capabilities, Practices, and Challenges: Insights from a Case Study , 2018, EASE.

[28]  Jessica Díaz,et al.  Why are many business instilling a DevOps culture into their organization? , 2020, ArXiv.

[29]  Carolyn B. Seaman,et al.  Qualitative Methods in Empirical Studies of Software Engineering , 1999, IEEE Trans. Software Eng..

[30]  유창조 Naturalistic Inquiry , 2022, The SAGE Encyclopedia of Research Design.

[31]  N. Denzin The research act: A theoretical introduction to sociological methods , 1977 .

[32]  Patrick Debois,et al.  Agile Infrastructure and Operations: How Infra-gile are You? , 2008, Agile 2008 Conference.

[33]  Fabio Kon,et al.  A Survey of DevOps Concepts and Challenges , 2020, ACM Comput. Surv..

[34]  Johnny Saldaña,et al.  The Coding Manual for Qualitative Researchers , 2009 .