Transitioning Towards Continuous Delivery in the B2B Domain: A Case Study
Delivering value to customers in real-time requires companies to utilize real-time deployment of software to expose features to users faster, and to shorten the feedback loop. This allows for faster reaction and helps to ensure that the development is focused on features providing real value. Continuous delivery is a development practice where the software functionality is deployed continuously to customer environment. Although this practice has been established in some domains such as B2C mobile software, the B2B domain imposes specific challenges. This article presents a case study that is conducted in a medium-sized software company operating in the B2B domain. The objective of this study is to analyze the challenges and benefits of continuous delivery in this domain. The results suggest that technical challenges are only one part of the challenges a company encounters in this transition. The company must also address challenges related to the customer and procedures. The core challenges are caused by having multiple customers with diverse environments and unique properties, whose business depends on the software product. Some customers require to perform manual acceptance testing, while some are reluctant towards new versions. By utilizing continuous delivery, it is possible for the case company to shorten the feedback cycles, increase the reliability of new versions, and reduce the amount of resources required for deploying and testing new releases.
KeywordsContinuous delivery Continuous deployment Development process B2B Case study
Unable to display preview. Download preview PDF.
- 1.Olsson, H. H., Alahyari, H., Bosch, J.: Climbing the “stairway to heaven”-a multiple-case study exploring barriers in the transition from agile development towards continuous deployment of software. In: 2012 38th EUROMICRO Conference on Software Engineering and Advanced Applications (SEAA), pp. 392–399. IEEE, September 2012Google Scholar
- 2.Neely, S., Stolt, S.: Continuous delivery? easy! just change everything (well, maybe it is not that easy). In: Agile Conference (AGILE), pp. 121–128. IEEE, August 2013Google Scholar
- 4.Humble, J., Farley, D.: Continuous delivery: reliable software releases through build, test, and deployment automation. Pearson Education (2010)Google Scholar
- 5.Humble, J., Read, C., North, D.: The deployment production line. In: Agile Conference, p. 6. IEEE, July 2006Google Scholar
- 6.Fowler, M.: ContinuousDelivery (January 2015). http://martinfowler.com/bliki/ContinuousDelivery.html
- 7.King, N.: Template analysis. In: Qualitative Methods and Analysis in Organizational Research: A Practical Guide, pp. 118–134. Sage Publications Ltd (1998)Google Scholar
- 10.Cockburn, A.: Agile software development. Cockburn* Highsmith Series Editor (2000)Google Scholar
- 11.Loshin, D.: Master data management. Morgan Kaufmann (2010)Google Scholar
- 12.Duvall, P. M., Matyas, S., Glover, A.: Continuous integration: improving software quality and reducing risk. Pearson Education (2007)Google Scholar
- 13.Rissanen, O., Münch, J., Männistö, T.: Extending the Development Process Towards Continuous Delivery and Continuous Experimentation in the B2B Domain: A Case Study. Master’s Thesis. University of Helsinki (2015)Google Scholar