Abstract
AbstractContinuous experimentation (CE) refers to a set of practices used by software companies to rapidly assess the usage, value, and performance of deployed software using data collected from customers and systems in the field using an experimental methodology. However, despite its increasing popularity in developing web‐facing applications, CE has not been studied in the development process of business‐to‐business (B2B) mission‐critical systems. By observing the CE practices of different teams, with a case study methodology inside Ericsson, we were able to identify the different practices and techniques used in B2B mission‐critical systems and a description and classification of the four possible types of experiments. We present and analyze each of the four types of experiments with examples in the context of the mission‐critical long‐term evolution (4G) product. These examples show the general experimentation process followed by the teams and the use of the different CE practices and techniques. Based on these examples and the empirical data, we derived the HURRIER process to deliver high‐quality solutions that the customers value. Finally, we discuss the challenges, opportunities, and lessons learned from applying CE and the HURRIER process in B2B mission‐critical systems.
Highlights
Companies are expected to continuously deliver fast, high-quality software that provides value to customers
This case study was conducted with a single company, we investigated continuous experimentation (CE) practices in multiple teams, areas, and products spread over six locations in four countries
In collaboration with Ericsson, we conducted a case study research method to understand how CE is used in B2B mission-critical systems
Summary
Companies are expected to continuously deliver fast, high-quality software that provides value to customers. The deployed software is becoming increasingly complex and has a high degree of interdependence with the operating environment These aspects make it hard for the development organization to evaluate the delivered value and the quality of the software.[1,2]. Fitzgerald and Stol[6] provide a review on several different initiatives around the term continuous They present a holistic view of the various software development activities throughout the entire software life cycle. Their work identified that most of the research with industry participation is in the context of web-facing companies such as
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
