68 research outputs found

    A systematic literature review on DevOps capabilities and areas

    Get PDF
    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

    Get PDF
    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

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

    Get PDF
    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

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

    Get PDF
    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

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

    Get PDF
    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

    Changing Software Development Practice: A Case Study of DevOps Adoption

    Get PDF
    DevOps, a portmanteau of development and operations, is a Software Engineering approach to emerge in industry, with a goal to rapidly develop and deploy good quality software. It has seen increased research attention in recent years with most studies focusing exclusively on tools used for DevOps or attempts to universally define it. This has led to a misunderstanding of DevOps alongside differing definitions, and therefore this research argues that a universal definition should not be sought. A focus group of practitioners evaluated existing definitions with the findings further tested in a questionnaire to the wider DevOps community. The output of this informed a 14 month case study of DevOps adoption in a medium sized UK organisation. A pragmatic approach was taken to study what DevOps meant for the organisation and its impact on employees and other business functions. This research contributes to theory by identifying the core attributes of DevOps, and by using a job crafting theoretical lens to understand the organisational change required to implement DevOps and elucidating how individuals change their work identity as they adopt DevOps practices and processes. In particular, this research finds that Software Developers are natural Job Crafters, especially if afforded the freedom to do so. This research contributes methodologically by using multiple methods, and in particular a longitudinal qualitative diary study over 14 months with a very low attrition rate. This was achieved through using tools that participants use in their work to record their experiences of DevOps implementation. Finally, this research makes a practical contribution by developing the building blocks of attributes that organisations should consider within their specific context and by developing an interdisciplinary framework that takes account of both the software development process and the associated management implications of adopting and implementing DevOps

    Lineamientos para la implementación del modelo CALMS de DevOps en mipymes desarrolladoras de software en el contexto surcolombiano

    Get PDF
    The term DevOps appears at 2009, it is a new paradigm, in which the developing process and deployment are integrated. Currently enterprises such as Etsy, Facebook, Amazon or Netflix are leaders in the implementation of DevOps paradigm. In this work, we present a guideline to implement the CALMS model (DevOps) at mipymes in the software development organizations of the South of Colombia. We present the technical and organizational aspects of guidelines; it integrates a newfangled development environment to develop of DevOps in the Colombian context. The purposed model was tested at mipymes from Colombia and the results are promising. The mipymes did a daily commit, when without of the guidelines they did a commit per week, in addition, 16 deployments were successful and upload to production, front 20 total deployments. Finally, we discuss how the implementation of the guidelines in an environment tested and integrated can be more productive organization, as well as how they can be competitive software companies in a globalized market.DevOps es un término relativamente nuevo que apareció por primera vez en 2009. Sin embargo, empresas como Etsy, Facebook, Amazon o Netflix son líderes en la implementación del nuevo paradigma. En este trabajo se presenta un conjunto de lineamientos para la implementación del modelo CALMS (DevOps) en mipymes de desarrollo de software en el contexto surcolombiano, así como un modelo que tiene en cuenta los aspectos técnicos y organizacio-nales para lograr un ambiente de desarrollo novedoso que permita la integración de DevOps al contexto del desarrollo de software colombiano. El modelo fue probado en una empresa mipyme y los resultados son alentadores. Se pasó de hacer un despliegue semanal a un despliegue diario, y de los 20 despliegues que se hicieron en total, 16 fueron puestos exitosamente en producción. Finalmente, discutimos cómo DevOps puede incrementar la productividad de las organizaciones de desarrollo de software y cómo la implementación de los lineamientos en un ambiente integrado y probado puede incrementar la competitividad de las empresas de software en un mercado globalizado

    Challenges in adopting a Devops approach to software development and operations

    Get PDF
    The constantly changing business needs and the requirement for faster time to market with software of present day has created a paradigm shift towards a 3rd generation Software Development philosophy called Devops. The lack of collaboration between IT Operations and Software Development as well as mismatch in configuration between development, testing and production environment has made deploying software releases slow and painful for many organizations. Different incentives between teams makes it difficult to work towards a common goal of bringing added value to customers. A Devops approach to software development brings down the walls between the teams and align incentives through a collaborative culture, automation, lean principles, measurement practices and sharing. The benefits of Devops have been shown to be substantial with a significantly faster time to market and increased software stability. The organizational change is substantial which makes the challenges in adopting Devops an interesting topic to research. This thesis studies the challenges of Devops by interviewing nine experts who had been involved with Devops initiatives in their companies. The qualitative study was conducted by semi-structured theme interviews on nine industry professionals who had hands-on experience with Devops implementations. The findings were divided into four main challenge categories based on their topic. Due to the novelty of the approach, the concept of Devops for many is unknown or biased which hurts the overall implementation of practices. The lack of support in both management and organizational levels is a hindrance, since especially changing culture needs strong support and organizational buy- in in order to succeed. The toolset needed for Devops is particularly diverse and finding the fit, correct usage and attitudes towards that technology is challenging. Finally, when shifting to Devops that requires a certain level of lean principles and agility, aligning existing organizational processes such as the change management process to accommodate the new way of working was found challenging. The implications of study yield four action points to help overcome the challenges found. Clearing misconceptions and spreading the knowledge of Devops helps overcome the lack of awareness challenge. Additionally, building commitment and trust in both management and team-levels getting Devops through the door in an organization. Establishing common ways of working and leading by example helps to overcome the challenge of fragmented technologies and reluctant attitudes towards it. Finally, ensuring the flexibility of the organization is key in order to prevent bottlenecks from forming in the delivery process
    corecore