Investigating Software Engineering Artifacts in DevOps Through the Lens of Boundary Objects

Software engineering artifacts are central to DevOps, enabling the collaboration of teams involved with integrating the development and operations domains. However, collaboration around DevOps artifacts has yet to receive detailed research attention. We apply the sociological concept of Boundary Objects to describe and evaluate the specific software engineering artifacts that enable a cross-disciplinary understanding. Using this focus, we investigate how different DevOps stakeholders can collaborate efficiently using common artifacts. We performed a multiple case study and conducted twelve semi-structured interviews with DevOps practitioners in nine companies. We elicited participants\u27 collaboration practices, focusing on the coordination of stakeholders and the use of engineering artifacts as a means of translation. This paper presents a consolidated overview of four categories of DevOps Boundary Objects and eleven stakeholder groups relevant to DevOps. To help practitioners assess cross-disciplinary knowledge management strategies, we detail how DevOps Boundary Objects contribute to four areas of DevOps knowledge and propose derived dimensions to evaluate their use

Report from GI-Dagstuhl Seminar 16394: Software Performance Engineering in the DevOps World

This report documents the program and the outcomes of GI-Dagstuhl Seminar 16394 "Software Performance Engineering in the DevOps World". The seminar addressed the problem of performance-aware DevOps. Both, DevOps and performance engineering have been growing trends over the past one to two years, in no small part due to the rise in importance of identifying performance anomalies in the operations (Ops) of cloud and big data systems and feeding these back to the development (Dev). However, so far, the research community has treated software engineering, performance engineering, and cloud computing mostly as individual research areas. We aimed to identify cross-community collaboration, and to set the path for long-lasting collaborations towards performance-aware DevOps. The main goal of the seminar was to bring together young researchers (PhD students in a later stage of their PhD, as well as PostDocs or Junior Professors) in the areas of (i) software engineering, (ii) performance engineering, and (iii) cloud computing and big data to present their current research projects, to exchange experience and expertise, to discuss research challenges, and to develop ideas for future collaborations

DevOps in Practice -- A preliminary Analysis of two Multinational Companies

DevOps is a cultural movement that aims the collaboration of all the stakeholders involved in the development, deployment and operation of soft-ware to deliver a quality product or service in the shortest possible time. DevOps is relatively recent, and companies have developed their DevOps prac-tices largely from scratch. Our research aims to conduct an analysis on practic-ing DevOps in +20 software-intensive companies to provide patterns of DevOps practices and identify their benefits and barriers. This paper presents the preliminary analysis of an exploratory case study based on the interviews to relevant stakeholders of two (multinational) companies. The results show the benefits (software delivery performance) and barriers that these companies are dealing with, as well as DevOps team topology they approached during their DevOps transformation. This study aims to help practitioners and researchers to better understand DevOps transformations and the contexts where the practices worked. This, hopefully, will contribute to strengthening the evidence regarding DevOps and supporting practitioners in making better informed decisions about the return of investment when adopting DevOps.Comment: 8 pages, 1 figure, 2 tables, conferenc

Performance assessment and analysis of development and operations based automation tools for source code management

Development and operations (DevOps), an accretion of automation tools, efficiently reaches the goals of software development, test, release, and delivery in terms of optimization, speed and quality. Diverse set of alternative automation tools exist for different phases of software development, for which DevOps adopts several selection criteria to choose the best tool. This research paper represents the performance evaluation and analysis of automation tools employed in the coding phase of DevOps culture. We have taken most commonly followed source code management tools-BitBucket, GitHub actions, and GitLab into consideration. Current work assesses and analyzes their performance based on DevOps evaluation criteria that too are categorized into different dimensions. For the purpose of performance evaluation, weightage and overall score is assigned to these criteria based on existing renowned literature and industrial case study of TekMentors Pvt Ltd. On the ground of performance outcome, the tool with the highest overall score is realized as the best source code automation tool. This performance analysis or measure will be a great benefit to our young researchers/students to gain an understanding of the modus operandi of DevOps culture, particularly source code automation tools. As a part of future research, other dimensions of selection criteria can also be considered for evaluation purposes

Factors that Influence the Synergy between Development and IT Operations in a DevOps Environment

Software development processes have been associated with severe conflicts between the development and operations teams. The problems further worsened by the occasional performance of activities such as planning, testing, integration, and releases. Many developing software development concepts reveal attempts to address these challenges. For instance, continuous integration is a practice that has emerged to reduce disconnects between development and IT operational deployments. In a comparable thread, the current emphasis on DevOps acknowledges that the integration between software development and its operational deployment needs to be a continuous whole. Problems involving the integration of software development and operations require positive synergy within DevOps teams. Team synergy brings about team effectiveness and performance as well as creating opportunities for innovation. The purpose of this study is to identify the factors that influence team synergy between the development and operations teams in a DevOps environment. The researcher conducted a case study at one of South Africa's leading information and communication technology services providers. Thirteen participants were interviewed to provide insight into the research questions. Interviews were conducted at the premises of the participating organization in Cape Town. The participants in the study preferred pseudonyms instead of their actual names to preserve anonymity. Interviews were transcribed and analysed using thematic analysis. During the analysis of the transcribed data, themes and categories were identified. The themes and categories that emerged from the data sources were aligned to the theoretical framework. The findings from this study describe enabling and inhibiting factors that influence the synergy between development and operations teams in a DevOps environment. Recognizing that DevOps teams face several challenges, the factors identified in this study provide insights into how organizations can influence the build and motivate their DevOps teams to achieve team synergy. The contribution to DevOps research is the application of a theoretical framework that suggests the importance of team social capital dimensions in the formation of team synergy. Based on its findings, this study recommends that further investigation and improvement on strategies to mitigate the factors that inhibit the dimensions of team social capital and prevent team synergy in a DevOps environment. The study also recommends a more detailed and practical demonstration to validate the value of the theoretical framework and continue to improve or extend it. This study revealed that DevOps teams operate in a complex and dynamic environment with many stakeholders and complex technical infrastructure. Based on this outcome, the study also suggests that future studies can take a different approach to create a different perspective on the synergy between DevOps teams by focusing on the behavior of the actors and complex problematic situations involving social activities