Understanding how DevOps aligns development and operations: a tripartite model of intra-IT alignment

Abstract

A top priority of organisations around the globe is to achieve IT-business alignment at all levels of the organisation. This paper addresses operational alignment within IT functions. Traditionally, IT functions are divided into highly independent subunits. In the face of pressure to adapt to rapidly changing customer demands and to manage increasingly complex IT architectures, many organisations have begun implementing joint, cross-functional DevOps teams, which integrate tasks, knowledge and skills pertaining to planning, building, and running software product activities. In this study, we examine eight cases of DevOps implementation. We apply grounded theory to identify three mechanisms comprising a tripartite model of intra-IT alignment: individual componentization, integrated responsibility, and multidisciplinary knowledge. Our model provides insights into how alignment between development and operations can be achieved in DevOps teams within the IT function.

Interruptions in Agile Software Development Teams

“…These interruptions are in line with the idea of interruptions as work impediments (Power & Conboy, 2015) and include missing information from fellow team members waiting for customer input and poorly specified requirements. Such impediments could be overcome by early integration and tight alignment with customers and operations departments (Maruping & Matook, 2020; Wiedemann et al, 2020). These interruptions were also caused by team configuration, such as restaffing, onboarding, or training team members, and assigning team members to multiple teams in parallel.…”

Obsolescence in IT Work: Causes, Consequences and Counter-Measures

“…A constant renewal of the skills and knowledge of IT professionals is necessary, as rapid technological change and other factors mean that old skills are no longer needed and demanded. For example, because of the pressure to adapt to rapidly changing customer requirements and manage increasingly complex IT architectures, many organizations have begun to establish joint cross-functional DevOps teams that integrate tasks, knowledge and skills related to the planning, building and operating of software product activities [66]. At the same time, skills may remain relevant beyond their actual obsolescence if systems based on obsolete technology are not fully replaced [23,[35][36][37].…”

Exploring the Benefits of Combining DevOps and Agile

“…Later, Patrick Debois coined the term DevOps (Development and Operations) and created the DevOps Day event [21]. Although the DevOps movement has been discussed for more than a decade [13][14][15]22] it still lacks a unique formal definition. For Wiedemann et al [23], the lack of a unique definition could be intentional to allow each team to choose the definition that better suits its needs.…”

“…In the literature, we can essentially find studies on DevOps that explore ways to align development teams with operations [15], the benefits that this methodology can bring to organizations [16], and the challenges that are posed [17]. However, there is a research gap in the characterization of the simultaneous adoption of Agile and DevOps in organizations.…”