Why and How do Large-scale Organizations Operationalize DevOps

An essential part of organizational efforts is to provide products to customers. To sustain competitive positions on existing markets, and to expand into new markets, firms utilize and continuously optimize approaches to efficiently provide effective products. Meanwhile, applying agile practices is a commoditized way for organizations to better adapt to changes during the development of their products. For bringing products to customers, more than their development is required. Typically, multiple organizational functions, all with individual goals and practices, are included in the development and delivery of products. This is often associated with friction points between those functions, and hinders the optimization of effectiveness and efficiency in providing products to customers. In retrospective, not all firms were able to recalibrate themselves and find back to former success after they had once missed to (again) innovate by timely addressing changes on their existing markets, discovering unmet or changed customer needs, and providing new products that bring together emerging technology with evolving customer demands. This potential threat now appears to be omnipresent with the ongoing proliferation of digitalization through the practical world of all of us. The emerging phenomenon of DevOps, a portmanteau word of “development” and “operations”, describes approaches to streamline development and delivery of products across organizational functions, to efficiently provide effective products, and to enable organizational digitalization efforts. This dissertation sheds light on reasoning, configurational factors, and dynamics behind DevOps implementations in large-scale. The composition of four independent yet interrelated scientific papers, the cornerstones of this dissertation, answers why and how large-scale organizations operationalize DevOps. In sum, this dissertation adds systematic and foundational knowledge, presents new applications and nuanced concretizations of scientific empiric approaches, connects allied but distinct research communities, and provides guidance for practitioners acting in this timely, relevant and interesting domain

After the success of DevOps introduce DataOps in enterprise culture

Dissertation presented as the partial requirement for obtaining a Master's degree in Information Management, specialization in Information Systems and Technologies ManagementA lot of organizations implemented DevOps processes with success. This allowed different areas like development, operations, security and quality work together. This cooperation, and processes associated to the work with these areas are producing excellent results. The organizations are developing many applications that support operation and are producing a lot of data. This data has a significant value for organizations because must be used in analysis, reporting and more recently data science projects to support decisions. It is time to take decisions supported in data and for this is necessary to transform organizations in a data-driven organizations and for this we need processes to deal with this data across all teams. This dissertation follows a design science research approach to apply multiple analytical methods and perspectives to create an artifact. The type of evidence within this methodology is a systematic literature review, with the goal to attain insights into the current state-of-the art research of DataOps implementation. Additionally, proven best practices from the industry are examined in depth to further strengthen the credibility. Thereby, the systematic literature review shall be used to pinpoint, analyze, and comprehend the obtainable empirical studies and research questions. This methodology supports the main goal of this dissertation, to develop and propose evidence-based practice guidelines for the DataOps implementation that can be followed by organizations

Relational Leadership, DevOps, and The Post-PC Era: Toward a Practical Theory for 21st Century Technology Leaders

This theoretically oriented scholarly personal narrative (SPN) explored how the constructionist view of relational leadership might be applied in a post-PC technological era marked by fast-paced innovation and an always on technology organization and infrastructure. Through reflecting on my personal and professional experience, I hope to offer the reflective scholar-practitioner new ways of thinking, present relational practices and suggest ways of being a leader participating in the fast-paced technology driven world. This new way of being combined both relational leadership and new DevOps practices that reduce organizational friction, break down departmental silos, and increase employee engagement in technology operations. Through this inquiry, I uncovered several practices and ways of being that are grounded in philosophical, theoretical, and social domains. In challenging the taken-for-granted reality of managing technology, I am attempting to produce practices for higher performance, humane, sustainable, and inspiring corporate information technology (IT) departments. The electronic version of this Dissertation is at AURA, http://aura.antioch.edu/etds/ and OhioLink ETD Center, www.ohiolink.edu/et

Relational Leadership, DevOps, and The Post-PC Era: Toward a Practical Theory for 21st Century Technology Leaders

This theoretically oriented scholarly personal narrative (SPN) explored how the constructionist view of relational leadership might be applied in a post-PC technological era marked by fast-paced innovation and an always ontechnology organization and infrastructure. Through reflecting on my personal and professional experience, I hope to offer the reflective scholar-practitioner new ways of thinking, present relational practices and suggest ways of being a leader participating in the fast-paced technology driven world. This new way of being combined both relational leadership and new DevOps practices that reduce organizational friction, break down departmental silos, and increase employee engagement in technology operations. Through this inquiry, I uncovered several practices and ways of being that are grounded in philosophical, theoretical, and social domains. In challenging the taken-for-granted reality of managing technology, I am attempting to produce practices for higher performance, humane, sustainable, and inspiring corporate information technology (IT) departments. For information regarding full-text access, please contact the author at: [email protected]

DevOps and information technology service management: A problem management case study

The use of DevOps is a predominant attribute of businesses engaged in the development and maintenance of Information Technology systems. Although literature exploring DevOps practices has expanded, there is still much unexplored territory on its operational ramifications. This is particularly observed when considering their potential impact on ITSM frameworks such as ITIL, which governs Operations. This research aims to establish how DevOps principles and practices can be applied to Problem Management, a core Service Management process. Specifically, it explores which DevOps practices may be used throughout the Problem lifecycle, as well as benefits which may result from them. An exploratory case study was carried out with the participation of Problem Managers operating in a DevOps environment. Three data collection methods were applied: Semi structured interviews, in which participants described their experience and insight in relation to DevOps and Problem Management; documental analysis and observation, where processes and workflows were examined; and a focus group exercise in which study outcomes were discussed and systematized. This research indicates that DevOps practices have varying degrees of significance for a Problem Management process. Practices associated with continuous planning and collaboration are prone to having greater significance in a Problem lifecycle, with the potential of enabling benefits such as quicker Problem identification, higher quality Root Cause Analysis, and improved resolution times. The novelty of insight gathered in this study benefits both academics, through its contribution to an expanding body of knowledge, and professionals, considering the practical and applicable nature of findings. Future work is also presented.A utilização de metodologias DevOps é hoje uma característica predominante de organizações envolvidas no desenvolvimento e manutenção de sistemas de Tecnologia e Informação. Apesar da crescente produção de literatura a examinar práticas DevOps, existe muito território por explorar referente às suas ramificações a nível operacional. Isto é particularmente notável quando se consideram potenciais interações com frameworks de ITSM como o ITIL, que governam Operações. Esta pesquisa tem como objetivo estabelecer quais princípios e práticas DevOps podem ser aplicadas na Gestão de Problemas, um processo central para a Gestão de Serviços. Especificamente, exploramos quais práticas DevOps podem ser utilizadas ao longo do ciclo de vida de um Problema, tal como que benefícios poderão resultar da sua aplicação. Um caso de estudo exploratório foi realizado com a participação de Gestores de Problemas a operar num ambiente DevOps. Três métodos de recolha de dados foram aplicados: Entrevistas semiestruturadas, onde participantes descreveram a sua experiência e conhecimento em relação a DevOps e Gestão de Problemas; análise documental e observação, onde processos operacionais foram examinados; e uma discussão em grupo onde resultados do estudo foram discutidos e sistematizados. Esta investigação indica que práticas DevOps tem variados níveis de significância para um processo de Gestão de Problemas. Práticas associadas ao planeamento contínuo e colaboração tendem a ter maior significância no ciclo de vida de um Problema, com potencial para gerar benefícios como a mais rápida identificação de Problemas, maior qualidade na análise de causa, e melhorias nos tempos de resolução. As conclusões apresentadas neste estudo trazem benefícios tanto para académicos, expandindo o corpo de conhecimento disponível sobre o tema, como para profissionais, considerando a sua natureza prática e aplicável. Direções para trabalho futuro são também apresentadas

Agile Processes in Software Engineering and Extreme Programming – Workshops

This open access book constitutes papers from the 5 research workshops, the poster presentations, as well as two panel discussions which were presented at XP 2021, the 22nd International Conference on Agile Software Development, which was held online during June 14-18, 2021. XP is the premier agile software development conference combining research and practice. It is a unique forum where agile researchers, practitioners, thought leaders, coaches, and trainers get together to present and discuss their most recent innovations, research results, experiences, concerns, challenges, and trends. XP conferences provide an informal environment to learn and trigger discussions and welcome both people new to agile and seasoned agile practitioners. The 18 papers included in this volume were carefully reviewed and selected from overall 37 submissions. They stem from the following workshops: 3rd International Workshop on Agile Transformation 9th International Workshop on Large-Scale Agile Development 1st International Workshop on Agile Sustainability 4th International Workshop on Software-Intensive Business 2nd International Workshop on Agility with Microservices Programmin

Exploring the development of a framework for agile methodologies to promote the adoption and use of cloud computing services in South Africa

The emergence of cloud computing is influencing how businesses develop, re-engineer, and implement critical software applications. The cloud requires developers to elevate the importance of compliance with security policies, regulations and internal engineering standards in their software development life cycles. Cloud computing and agile development methodologies are new technologies associated with new approaches in the way computing services are provisioned and development of quality software enhanced. However adoption and use of agile and cloud computing by SMMEs in South Africa is seemingly constrained by a number of technical and non-technical challenges. Using Grounded Theory and case study method this study was aimed at exploring the development of a framework for agile methodologies to promote the adoption and use of cloud computing services by SMMEs in South Africa. Data was collected through survey and in-depth interviews. Open, Axial and Selective coding was used to analyse the data. In tandem with its main objective the study, besides exploring the development of the envisaged framework, also generated and made available valuable propositions and knowledge that SMMEs in South Africa using agile development methodologies can use to work better with cloud computing services in the country without compromising on software quality. The findings of this study and the emerging insights around the development of the framework, which in itself also constitutes an important decision making tool for supporting adoption and use of cloud computing services, are a substantial contribution to knowledge and practice in the ICT field of information systems in South AfricaInformation ScienceD. Phil. (Information Systems

Continuous Rationale Management

Continuous Software Engineering (CSE) is a software life cycle model open to frequent changes in requirements or technology. During CSE, software developers continuously make decisions on the requirements and design of the software or the development process. They establish essential decision knowledge, which they need to document and share so that it supports the evolution and changes of the software. The management of decision knowledge is called rationale management. Rationale management provides an opportunity to support the change process during CSE. However, rationale management is not well integrated into CSE. The overall goal of this dissertation is to provide workflows and tool support for continuous rationale management. The dissertation contributes an interview study with practitioners from the industry, which investigates rationale management problems, current practices, and features to support continuous rationale management beneficial for practitioners. Problems of rationale management in practice are threefold: First, documenting decision knowledge is intrusive in the development process and an additional effort. Second, the high amount of distributed decision knowledge documentation is difficult to access and use. Third, the documented knowledge can be of low quality, e.g., outdated, which impedes its use. The dissertation contributes a systematic mapping study on recommendation and classification approaches to treat the rationale management problems. The major contribution of this dissertation is a validated approach for continuous rationale management consisting of the ConRat life cycle model extension and the comprehensive ConDec tool support. To reduce intrusiveness and additional effort, ConRat integrates rationale management activities into existing workflows, such as requirements elicitation, development, and meetings. ConDec integrates into standard development tools instead of providing a separate tool. ConDec enables lightweight capturing and use of decision knowledge from various artifacts and reduces the developers' effort through automatic text classification, recommendation, and nudging mechanisms for rationale management. To enable access and use of distributed decision knowledge documentation, ConRat defines a knowledge model of decision knowledge and other artifacts. ConDec instantiates the model as a knowledge graph and offers interactive knowledge views with useful tailoring, e.g., transitive linking. To operationalize high quality, ConRat introduces the rationale backlog, the definition of done for knowledge documentation, and metrics for intra-rationale completeness and decision coverage of requirements and code. ConDec implements these agile concepts for rationale management and a knowledge dashboard. ConDec also supports consistent changes through change impact analysis. The dissertation shows the feasibility, effectiveness, and user acceptance of ConRat and ConDec in six case study projects in an industrial setting. Besides, it comprehensively analyses the rationale documentation created in the projects. The validation indicates that ConRat and ConDec benefit CSE projects. Based on the dissertation, continuous rationale management should become a standard part of CSE, like automated testing or continuous integration

Good Practices of the Lean Startup Methodology: Benefits, challenges and recommendations

Most companies strive to capitalize on new business opportunities to innovate and develop new business models. The recent popularity of Lean Startup methodology in the startup scene suggests its potential applicability for the creation of new businesses in a corporate context. Therefore, this thesis identifies how to apply Lean Startup practices in software companies. The research was conducted as a literature review and a qualitative study, including semi-structured interviews from three Finnish software companies. Furthermore, the study provides a within-case and cross-case analysis of the positive and negative effects and recommendations for applying Lean Startup practices in software companies. The results indicate that there is resistance to change towards a more innovative company culture, insufficient knowledge and understanding of the Lean Startup, and its practices require time to be learnt. Moreover, the lack of proper communication of the Lean Startup benefits creates rejection from external teams. Nevertheless, the results reveal that the top management commitment to communicate and demonstrate early on what the Lean Startup is can help software companies and customers accept more readily the methodology and shift the company culture mindset towards a more innovative mindset. Furthermore, the results confirm that the Lean Startup application adds customer validation to the product development process, enabling faster product/market fits and data-driven decision-making that improves the process accuracy and speed. Moreover, the innovation accounting practice supports the learning about customer behavior. In contrast, the results show that teams not working together in the same location, customers rigidness and low or high volume of feedback can reduce the product development process speed. Consequently, software companies should communicate and demonstrate very early on the benefits of the Lean Startup methodology to employees and customers to help them understand, learn and adopt its practices while embracing a more innovative culture