DevOps maturity in an IT service environment

Table of Contents

1. Introduction

1.1. Motivation

1.2. Research Questions

1.3. Research Design

1.4. Outline / Remainder

2. Research Methods

2.1. Literature Review Methods

2.2. Empirical Methods

3. Literature Review

3.1. Scope

3.2. Research Process

3.2.1. Systematic Literature Review

3.2.2. Targeted Review

3.3. Results

3.3.1. Systematic Literature Review

3.3.2. Targeted Review

4. Empirical Research

4.1. Case Description

4.2. Research Process

4.3. Results

4.3.1. Practitioner Perception of DevOps

4.3.2. Model Revision, Iteration 1

4.3.3. Model Revision, Iteration 2

5. The DevOps Assessment Model

5.1. Model Presentation

5.1.1. The DevOps Mindset Assessment

5.1.2. The DevOps Capability Assessment

5.2. Model Development

5.3. Managerial Implications on Using the DevOps Assessment Model

6. Evaluation

6.1. Summative

6.2. Formative

7. Discussion, Limitations, Future Research

Research Objectives and Key Topics

This thesis aims to clarify the ambiguous term "DevOps" by identifying its core characteristics and implementation criteria. Through a synthesis of existing literature and empirical research conducted within an IT service organization, the work develops and validates a maturity model designed to help practitioners assess their organization’s DevOps performance and identify areas for improvement.

• Characterization of DevOps via systematic literature review.
• Development of a research-based DevOps Assessment Model.
• Application of Action Design Research (ADR) to refine the model.
• Evaluation of DevOps maturity within different organizational environments.
• Identification of managerial implications for successful DevOps adoption.

Excerpt from the Book

Summary of Chapters

1. Introduction: This chapter provides the motivation for the study, defines the research questions, and outlines the overall research design and the structure of the thesis.

2. Research Methods: This section details the application of Action Design Research (ADR) and the specific qualitative methods, including the systematic literature review and Problem-centered Interviews, utilized in the study.

3. Literature Review: The chapter synthesizes existing academic knowledge to characterize DevOps, defining its principles, practices, and outcomes based on current literature.

4. Empirical Research: This chapter describes the practical research conducted at an IT service organization, presenting stakeholder perceptions and the iterative process of model refinement.

5. The DevOps Assessment Model: The final state of the maturity model is presented, including both the "Mindset" and "Capability" assessments, along with an explanation of its development phases.

6. Evaluation: This chapter details the evaluation of the model through workshops in different divisions, assessing its usability and effectiveness in practice.

7. Discussion, Limitations, Future Research: The thesis concludes by discussing the findings, addressing the limitations of the research, and suggesting directions for future scientific inquiry.

Keywords

DevOps, Maturity Model, IT Service Management, Continuous Delivery, Action Design Research, Software Development, Organizational Culture, Infrastructure as Code, Automation, Systems Thinking, Collaboration, Lean Startup, Continuous Integration, Continuous Deployment, IT Operations.

Frequently Asked Questions

What is the primary focus of this thesis?

The thesis focuses on defining the term "DevOps" and developing a research-based maturity model to help organizations assess their current DevOps practices and guide implementation improvements.

Which central topics are explored in the work?

Central topics include the cultural and organizational shifts required for DevOps, the role of automation and continuous delivery in IT, and the bridging of silos between development and operations teams.

What is the main research question of this study?

The research is guided by five questions, primarily aiming to identify key DevOps characteristics, translate them into measurable indicators, and determine how a maturity model can be used to assess and improve an organization’s performance.

Which scientific methodology is applied?

The study employs Action Design Research (ADR), which allows for the iterative construction and evaluation of an IT artifact—in this case, the DevOps Assessment Model—through interaction with practitioners.

What does the main part of the thesis cover?

The main body covers a comprehensive systematic literature review, empirical research conducted through Problem-centered Interviews in an IT service environment, and the multi-stage design and evaluation of the DevOps Assessment Model.

How is the DevOps Assessment Model characterized?

The model is described as a "prescriptive" maturity model, intended to provide organizations with an overview of their maturity while offering guidance on how to approach improvements to gain business value.

Why did the author separate the model into "Mindset" and "Capability"?

The separation was made because the cultural "Mindset" aspects (related to values) are best assessed by human estimation, whereas technological and organizational "Capabilities" can be assessed through clearly defined, objective maturity levels.

How did practitioners influence the development of the model?

Practitioners provided feedback through interviews and workshops, which helped refine the model's items, clarify terminology, and ensure the criteria were practical and relevant for their specific IT service environment.

What is the significance of the "Pre-DevOps" stage?

The "Pre-DevOps" (or level zero) stage acts as an entry point for organizations that have not yet begun adopting DevOps practices, allowing them to identify their initial state within the maturity scale.