A grounded theory of organizational structures for development and infrastructure professionals in software-producing organizations

Leite, Leonardo

doi:10.11606/t.45.2022.tde-28062022-132626

Cited by 1 publication

(1 citation statement)

References 58 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We chose document D1 and D2* because they present four DevOps Team structures and their properties. We chose the latest research updates from the document D2, which we labeled as D2* [29]. Finally, document D7 presents only one team structure.…”

Section: Representativeness Of the Theorymentioning

confidence: 99%

Harmonizing DevOps Taxonomies - A Grounded Theory Study

Díaz

Pérez

Alves³

et al. 2022

Preprint

View full text Add to dashboard Cite

Context: DevOps responds to the growing need of companies to streamline the software development process and, thus, have experienced a widespread adoption in the past few years. However, successful adoption of DevOps requires companies to address important cultural and organizational changes. Understanding the organizational structure and characteristics of teams adopting DevOps is key, and comprehending the existing theories and representations of team taxonomies is critical to guide companies in a more systematic and structured DevOps adoption process. Objective: This paper presents empirical research on the structure of DevOps teams in software-producing organizations. The goal is to better understand the organizational structure and characteristics of teams adopting DevOps by harmonizing the existing knowledge. Method: To do this, we conducted a grounded theory study, analyzing existing studies on DevOps teams and taxonomies. Results: From the analysis, we built a substantive and analytic theory of DevOps taxonomies. The theory is substantive in that the scope of validity refers to the ten primary studies processed and analytic in that it analyzes “what is” rather than explaining causality or attempting predictive generalizations. A public repository with all the data related to the products resulting from the analysis and generation of the theory is available. Conclusions: We built a theory on DevOps taxonomies and tested whether it harmonizes the existing taxonomies, i.e., whether our theory can instantiate the others. This is the first step to define which taxonomies are best suited to approach DevOps culture and practices according to the companies’ objectives and capabilities.

show abstract

Section: Representativeness Of the Theorymentioning

confidence: 99%