Klotins, EriksTalbert-Goldstein, Elliot2023-06-122023-06-122023-05-20Klotins, E., Talbert-Goldstein, E. (2023). Organizational Conflicts in the Adoption of Continuous Software Engineering. In: Stettina, C.J., Garbajosa, J., Kruchten, P. (eds) Agile Processes in Software Engineering and Extreme Programming. XP 2023. Lecture Notes in Business Information Processing, vol 475. Springer, Cham. https://doi.org/10.1007/978-3-031-33976-9_10https://doi.org/10.1007/978-3-031-33976-9_10http://hdl.handle.net/11603/28167XP 2023, Amsterdam, The Netherlands, June 13-16, 2023.Software is a critical component of nearly every product or service. Improvements in software can lead to substantial competitive advantages. At the same time, software and surrounding engineering teams have become increasingly complex. The adoption of continuous integration and delivery is a recent trend to radically improve software release speed. However, its adoption is far from straightforward. Specifically, rethinking processes, organizational culture, ways of working, and business models require buy-in from diverse stakeholders that may have conflicting objectives. Such situations are explored by organizational conflict research. This paper reports on early lessons from an ongoing research project in continuous software engineering, specifically investigating adoption challenges from an organizational conflict perspective. We identify catalysts, symptoms, and outcomes of organizational conflicts hindering the adoption process. We conclude that predictable conflicts emerge when adopting continuous engineering. Engineers, managers, and other teams can proactively prepare for and allocate resources to resolve them. Proper analysis and management can help avoid wasted time, impeding processes, and frustration.16 pagesen-USThis item is likely protected under Title 17 of the U.S. Copyright Law. Unless on a Creative Commons license, for uses protected by Copyright Law, contact the copyright holder or the author.Attribution 4.0 International (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/Empirical and Applied Software Engineering Lab (EASEL)Text