Advertisement

Challenges When Adopting Continuous Integration: A Case Study

  • Adam Debbiche
  • Mikael Dienér
  • Richard Berntsson Svensson
Part of the Lecture Notes in Computer Science book series (LNCS, volume 8892)

Abstract

The complexity of software development has increased over the last few years. Customers today demand higher quality and more stable software with shorter delivery time. Software companies strive to improve their processes in order to meet theses challenges. Agile practices have been widely praised for the focus they put on customer collaboration and shorter feedback loops. Companies that have well established agile practices have been trying to improve their processes further by adopting continuous integration - the concept where teams integrate their code several times a day. However, adopting continuous integration is not a trivial task. This paper presents a case study in which we, based on interviews at a major Swedish telecommunication services and equipment provider, assess the challenges of continuous integration. The study found 23 adoption challenges that organisations may face when adopting the continuous integration process.

Keywords

continuous integration software challenges 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Braun, V., Clarke, V.: Using thematic analysis in psychology. Qualitative Research in Psychology 3(2), 77–101 (2006)CrossRefGoogle Scholar
  2. 2.
    Claps, G.: Continuous Deployment: An Examination of the Technical and Social Adoption Challenges. diploma thesis, The University of New South Wales (2012)Google Scholar
  3. 3.
    Conboy, K., Coyle, S., Wang, X., Pikkarainen, M.: People over process: Key challenges in agile development. IEEE Software 28(4), 48–57 (2011)CrossRefGoogle Scholar
  4. 4.
    Deependra, M.: Managing change for software process improvement initiatives: A practical experience-based approach.  4(4), 199–207 (1998)Google Scholar
  5. 5.
    Fowler, M.: Continuous integration @ONLINE (May 2006), http://martinfowler.com/articles/continuousIntegration.html
  6. 6.
    Goodman, D., Elbaz, M.: It’s not the pants, it’s the people in the pants, learnings from the gap agile transformation what worked, how we did it, and what still puzzles us. In: Agile Conference AGILE 2008, pp. 112–115 (August 2008)Google Scholar
  7. 7.
    Holck, J., Jørgensen, N.: Continuous integration and quality assurance: A case study of two open source projects. Australasian J. of Inf. Systems 11(1) (2003)Google Scholar
  8. 8.
    Humble, J., Farley, D.: Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation, 1st edn. Addison-Wesley Professional (2010)Google Scholar
  9. 9.
    Klein, H., Myers, M.: A set of principles for conducting and evaluating interpretive field studies in information systems. MIS Quarterly 23(1), 67–93 (1999)CrossRefGoogle Scholar
  10. 10.
    Kotter, J.P.: Leading change: Why transformation efforts fail. Harvard Business Review 85(1), 96 (2007)MathSciNetGoogle Scholar
  11. 11.
    Lacoste, F.: Killing the gatekeeper: Introducing a continuous integration system. In: Agile Conference, AGILE 2009, pp. 387–392 (2009)Google Scholar
  12. 12.
    Mathiassen, L., Ngwenyama, O., Aaen, I.: Managing change in software process improvement. IEEE Software 22(6), 84–91 (2005)CrossRefGoogle Scholar
  13. 13.
    Miller, A.: A hundred days of continuous integration. In: Agile Conference, AGILE 2008, pp. 289–293 (August 2008)Google Scholar
  14. 14.
    Olsson, 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: 38th EUROMICRO Conference on Software Engineering and Advanced Applications, pp. 392–399 (September 2012)Google Scholar
  15. 15.
    Robson, C.: Real World Research: A Resource for Social Scientists and Practitioner-Researchers. Regional Surveys of the World Series. Wiley (2002)Google Scholar
  16. 16.
    Runeson, P., Höst, M.: Guidelines for conducting and reporting case study research in software engineering. Empirical Software Engineering 14(2), 131–164 (2009)CrossRefGoogle Scholar
  17. 17.
    Ståhl, D., Bosch, J.: Modeling continuous integration practice differences in industry software development. J. Syst. Softw. 87, 48–59 (2014)CrossRefGoogle Scholar
  18. 18.
    Turk, D., France, R., Rumpe, B.: Assumptions underlying agile software-development processes. Journal of Database Management 16(4), 62–87 (2005)CrossRefGoogle Scholar
  19. 19.
    Van Der Storm, T.: Backtracking incremental continuous integration. In: 12th European Conference on Software Maintenance and Reengineering, CSMR 2008, pp. 233–242 (2008)Google Scholar
  20. 20.
    Yin, R.K.: Case study research: Design and methods. Sage (1994)Google Scholar

Copyright information

© Springer International Publishing Switzerland 2014

Authors and Affiliations

  • Adam Debbiche
    • 1
  • Mikael Dienér
    • 1
  • Richard Berntsson Svensson
    • 2
  1. 1.Department of Computer Science and EngineeringChalmersGothenburgSweden
  2. 2.Department of Computer Science and EngineeringChalmers,University of GothenburgGothenburgSweden

Personalised recommendations