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.

[1]  Alistair Cockburn,et al.  Agile Software Development , 2001 .

[2]  David Loshin Master Data Management , 2008 .

[3]  Tony Gorschek,et al.  Social networks in software process improvement , 2010 .

[4]  Jan Bosch,et al.  Building Products as Innovation Experiment Systems , 2012, ICSOB.

[5]  Steve Neely,et al.  Continuous Delivery? Easy! Just Change Everything (Well, Maybe It Is Not That Easy) , 2013, 2013 Agile Conference.

[6]  Jan Bosch,et al.  Climbing the "Stairway to Heaven" -- A Mulitiple-Case Study Exploring Barriers in the Transition from Agile Development towards Continuous Deployment of Software , 2012, 2012 38th Euromicro Conference on Software Engineering and Advanced Applications.

[7]  H. Bussell Qualitative Methods and Analysis in Organizational Research: A Practical Guide , 2000 .

[8]  Jez Humble,et al.  Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation , 2010 .

[9]  Andrew Glover,et al.  Continuous Integration: Improving Software Quality and Reducing Risk (The Addison-Wesley Signature Series) , 2007 .

[10]  Jez Humble,et al.  The deployment production line , 2006, AGILE 2006 (AGILE'06).

[11]  J. Gerring A case study , 2011, Technology and Society.

[12]  Jürgen Münch,et al.  Continuous Experimentation in the B2B Domain: A Case Study , 2014, 2015 IEEE/ACM 2nd International Workshop on Rapid Continuous Software Engineering.

[13]  Per Runeson,et al.  Guidelines for conducting and reporting case study research in software engineering , 2009, Empirical Software Engineering.