Abstract
Software is becoming a critical component of most products and organizational functions. The ability to continuously improve software determines how well the organization can respond to market opportunities. Continuous software engineering promises numerous advantages over sprint-based or plan-driven development. However, implementing a continuous software engineering pipeline in an existing organization is challenging.
In this invited position paper, we discuss the adoption challenges and argue for a more systematic methodology to drive the adoption of continuous engineering. Our discussion is based on ongoing work with several industrial partners as well as experience reported in both state-of-practice and state-of-the-art.
We conclude that the adoption of continuous software engineering primarily requires analysis of the organization, its goals, and constraints. One size does not fit all purposes, meaning that many of the principles behind continuous engineering are relevant for most organizations, but the level of realization and the benefits may still vary. The main hindrances to continuous flow of software arise from sub-optimal organizational structures and the lack of alignment. Once those are removed, the organization can implement automation to further improve the software delivery.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Similar content being viewed by others
References
Fitzgerald, B., Stol, K.J.: Continuous software engineering: a roadmap and agenda. J. Syst. Softw. 123, 176–189 (2017)
Humble, J., Kim, G.: Accelerate: The science of lean software and DevOps: Building and scaling high performing technology organizations. IT Revolution (2018)
Khurum, M., Gorschek, T., Wilson, M.: The software value map-an exhaustive collection of value aspects for the development of software intensive products. J. Softw. Evol. Process 25(7), 711–741 (2013)
Klotins, E., Gorschek, T.: Towards cost-benefit evaluation for continuous* software engineering activities. Rev. Empir. Softw. Eng. J. (2021)
Klotins, Eriks, P.A.E.: The unified perspective of digital transformation and continuous software engineering. In: Proceedings of 5th International Workshop on Software-Intensive Business (IWSIB) (2022)
Poppendieck, M., et al.: Principles of lean thinking. IT Manage. Select 18(2011), 1–7 (2011)
Shahin, M., Babar, M.A., Zhu, L.: Continuous integration, delivery and deployment: a systematic review on approaches, tools, challenges and practices. IEEE Access 5, 3909–3943 (2017)
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2022 Springer Nature Switzerland AG
About this paper
Cite this paper
Klotins, E., Gorschek, T. (2022). Continuous Software Engineering in the Wild. In: Mendez, D., Wimmer, M., Winkler, D., Biffl, S., Bergsmann, J. (eds) Software Quality: The Next Big Thing in Software Engineering and Quality. SWQD 2022. Lecture Notes in Business Information Processing, vol 439. Springer, Cham. https://doi.org/10.1007/978-3-031-04115-0_1
Download citation
DOI: https://doi.org/10.1007/978-3-031-04115-0_1
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-031-04114-3
Online ISBN: 978-3-031-04115-0
eBook Packages: Computer ScienceComputer Science (R0)