A Survey of DevOps in the South African Software Context

This study investigated DevOps practices and experiences in the South African software development context, along with associated perceptions of benefits and challenges. Survey data collected from a sample of 80 software development professionals showed that more frequent builds, earlier detection of bugs and reduced project lead times were the top three benefits, while getting DevOps capable members into a team, finding experienced professionals to support DevOps practice and changing deep-seated company culture to support DevOps were the top three challenges. DevOps practices are still emerging. Although 85% of respondents report continuous integration as a frequent practice, only 54% report using continuous deployment frequently. The biggest reported impacts of DevOps on software development culture were in making development team members aware of operational faults, responsible for quality assurance, and responsible for deployments. Realisation of benefits from DevOps depends largely on a culture change. Results are useful for guiding organisations considering DevOps adoption

DevOps model in practice: Applying a novel reference model to support and encourage the adoption of DevOps in a software development company as case study

DevOps has emerged as an approach to help organizations automate, cost optimization, increase profitability, improve the stability of the software development process and the responsiveness of organizations, and create a more agile development and release pipeline. However, its adoption, maintenance and evaluation continue to be a challenge for software organizations, due to the absence of solutions that formalize process elements in a detailed way, such as: practices, roles, artifacts, objectives, among others. This paper presents a DevOps Model, this model to support the adoption of DevOps, which provides a set of fundamental and complementary values, principles, dimensions, and practices. The practices suggest a set of items such as purpose, specific objectives and expected artifacts. The elements defined in proposed DevOps Model arise from the elements found in the studies analyzed through a systematic mapping study. Model evaluation was carried out through a software development company as case study. The results obtained have allowed the case study company to evaluate, diagnose and identify improvement opportunities to be carried out in the processes and projects where a DevOps-based approach is used, the above in a practical, useful, and adequate way that allows this type of companies and with a low use of resources, both economic investment and time. This is how the DevOps Model could guide professionals and organizations towards a better understanding of DevOps, in addition to minimizing the subjectivity and error of its interpretation, adoption and evaluation

A systematic literature review on DevOps capabilities and areas

Businesses today need to respond to customer needs at an unprecedented speed. Driven by this need for speed, many companies are rushing to the DevOps movement. DevOps, the combination of Development and Operations, is a new way of thinking in the software engineering domain that recently received much attention. Since DevOps has recently been introduced as a new term and novel concept, no common understanding of what it means has yet been achieved. Therefore, the definitions of DevOps often are only partly relevant to the concept. This research presents a systematic literature review to identify the determining factors contributing to the implementation of DevOps, including the main capabilities and areas with which it evolves.info:eu-repo/semantics/acceptedVersio

Team management strategies for DevOps

In an increasingly digital market, and where the time to market is shorter and the quality and reliability more relevant, it is imperative that software development teams can organize themselves in order to provide a faster reaction to the market with more reliability. DevOps intends to eliminate the existence of silos (Development and Operations) and streamline the software production, declining waste and difficulties in its construction, increasing productivity and developing better products with a focus on client satisfaction. Nevertheless, the joining of teams around the same goal causes key managing challenges, namely the management of conflicts and information sharing between teams. The way that these challenges are managed can interfere with the successful implementation of DevOps philosophy. Though a Case Study, the research goal is to study the best team management strategies that help to reduce the appearance of conflicts and enhance information sharing in the context of DevOps implementation, increasing effectiveness in those teams. As a result, this research brings some strategies to facilitate the DevOps team management and reinforces the importance of managing conflicts, processes, tasks and information well.Num mercado cada vez mais digital e onde o tempo de mercado é cada vez mais curto, a qualidade e fiabilidade mais relevantes, é imperativo que as equipas de desenvolvimento de software consigam organizar-se de modo a proporcionar uma resposta rápida no mercado e cada vez mais fiável. A filosofia DevOps pretende terminar com a existência de silos (Desenvolvimento e Operações) e agilizar a produção de software, diminuindo desperdício e dificuldades na sua construção, aumentando a produtividade e desenvolver produtos melhores com foco na satisfação do cliente. Contudo, a junção de equipas em torno de um mesmo objetivo acarreta desafios cruciais para a gestão, nomeadamente a gestão de conflitos e da informação entre as equipas. A forma como estes desafios são geridos poderá interferir no sucesso da implementação de uma filosofia DevOps. Através de um Caso de Estudo, o objetivo desta pesquisa é o levantamento das melhores estratégias de gestão de equipas que ajudem a reduzir o surgimento de conflitos e potenciar a partilha de informação em contexto de implementação da filosofia DevOps, aumentando a eficácia destas equipas. Como resultado, esta pesquisa traz algumas estratégias que podem facilitar a gestão de equipas DevOps e reforça a importância de fazer uma boa gestão dos conflitos, tarefas, processos e da informação

A Systematic Literature Review on DevOps and its Definitions, Adoptions, Benefits and Challenges

The increased pace of software development and rapid changes of business- and technological requirements have introduced a new type of software development culture called DevOps. IT Operations and Software Development have endured poor communication and collaboration with each other, which have resulted in bottlenecks throughout the software development life cycle. The discrepancy has contributed to delayed software updates with inferior quality and a culture, that complicates the goals of organisations, to produce high-quality software for its customers. DevOps can streamline the software development process by removing the constraints on the teams, by increasing collaboration, automation, sharing and measurement principles. This is possible through the change of mindset and culture of the organisation. Since the concept of DevOps is loosely defined, it is an interesting topic to research. This thesis provides an insight on the definitions, implementations, benefits and challenges of DevOps, through a systematic literature review. The literature review was conducted by identifying and analysing the related literature on DevOps. The results were 25 primary studies on the definition, adoption methods, benefits and challenges of DevOps. The result presents ways to define DevOps, some tools and methods on how to adopt DevOps within an organisation and some perceived benefits and challenges of adopting DevOps. The contribution of the thesis provides an overall understanding of DevOps and its core principles and practices. The contribution also includes, approaches for adopting DevOps, the premise behind its adoption and obstacles that may occur during the process

A maturity model for DevOps

Nowadays, businesses aim to respond to customer needs at unprecedented speed. Thus, many companies are rushing to the DevOps movement. DevOps is the combination of Development and Operations and a new way of thinking in the software engineering domain. However, no common understanding of what it means has yet been achieved. Also, no adoption models or fine-grained maturity models to assist DevOps maturation and implementation were identified. Therefore, this research attempt to fill these gaps. A systematic literature review is performed to identify the determining factors contributing to the implementation of DevOps, including the main capabilities and areas with which it evolves. Then, two sets of interviews with DevOps experts were performed and their experience used to build the DevOps Maturity Model. The DevOps maturity model was then developed grounded on scientific and professional viewpoints. Once developed the Maturity Model was demonstrated in a real organisation.info:eu-repo/semantics/acceptedVersio

Maturity model for DevOps

Businesses today need to respond to customer needs at unprecedented speed. Driven by this need for speed, many companies are rushing to the DevOps movement. DevOps, the combination of Development and Operations, is a new way of thinking in the software engineering domain that recently received much attention. Since DevOps has recently been introduced as a new term and novel concept, no common understanding of what it means has yet been achieved. Therefore, the definitions of DevOps often are only a part relevant to the concept. When further observing DevOps, it could be seen as a movement, but is still young and not yet formally defined. Also, no adoption models or fine-grained maturity models showing what to consider to adopt DevOps and how to mature it were identified. As a consequence, this research attempted to fill these gaps and consequently brought forward a Systematic Literature Review to identify the determining factors contributing to the implementation of DevOps, including the main capabilities and areas with which it evolves. This resulted in a list of practices per area and capability that was used in the interviews with DevOps practitioners that, with their experience, contributed to define the maturity of those DevOps practices. This combination of factors was used to construct a DevOps maturity model showing the areas and capabilities to be taken into account in the adoption and maturation of DevOps.Hoje em dia, as empresas precisam de responder às necessidades dos clientes a uma velocidade sem precedentes. Impulsionadas por esta necessidade de velocidade, muitas empresas apressam-se para o movimento DevOps. O DevOps, a combinação de Desenvolvimento e Operações, é uma nova maneira de pensar no domínio da engenharia de software que recentemente recebeu muita atenção. Desde que o DevOps foi introduzido como um novo termo e um novo conceito, ainda não foi alcançado um entendimento comum do que significa. Portanto, as definições do DevOps geralmente são apenas uma parte relevante para o conceito. Ao observar o DevOps, o fenómeno aborda questões culturais e técnicas para obter uma produção mais rápida de software, tem um âmbito amplo e pode ser visto como um movimento, mas ainda é jovem e ainda não está formalmente definido. Além disso, não foram identificados modelos de adoção ou modelos de maturidade refinados que mostrem o que considerar para adotar o DevOps e como fazê-lo crescer. Como consequência, esta pesquisa tentou preencher essas lacunas e, consequentemente, apresentou uma Revisão sistemática da literatura para identificar os fatores determinantes que contribuem para a implementação de DevOps, incluindo os principais recursos e áreas com os quais ele evolui. Isto resultou numa lista de práticas por área e por capacidade, que foi utilizado como base nas entrevistas realizadas com peritos em DevOps que, com a sua experiência, ajudaram a atribuir níveis de maturidade a cada prática. Esta combinação de fatores foi usada para construir um modelo de maturidade de DevOps mostrando as áreas e as capacidades a serem levados em consideração na sua adoção e maturação

Examination of Adoption Theory on the DevOps Practice of Continuous Delivery

Many organizations have difficulty adopting advanced software development practices. Some software development project managers in large organizations are not aligned with the relationship between performance expectancy, effort expectancy, social influence, and facilitating conditions, as moderated by experience, with intent to adopt the DevOps practice of continuous delivery. The purpose of this study was to examine the statistical relationships between the independent variablesâperformance expectancy, effort expectancy, social influence, and facilitating conditions, as moderated by experienceâand the dependent variable of behavioral intent to adopt a continuous delivery system. Venkatesh, Morris, Davis, and Davis\u27s unified theory of acceptance and use of technology provided the theoretical framework. A stepwise multiple linear regression analysis was performed on survey data from 85 technical project managers affiliated with LinkedIn project management groups. The analysis reflected that only performance expectancy was significant in predicting intent to adopt continuous delivery. The findings may contribute to social change by providing project managers with the information they need to support organizational change, collaboration, and facilitation. The knowledge gained may additionally help organizations develop operational efficiency, competitive advantage, and generate higher value to their clients and society