Tampere University of Technology

TUTCRIS Research Portal

Revisiting continuous deployment maturity: A two-year perspective

Research output: Chapter in Book/Report/Conference proceedingConference contributionScientificpeer-review

Details

Original languageEnglish
Title of host publicationProceedings of the 34th ACM/SIGAPP Symposium on Applied Computing
PublisherACM
Pages1810-1817
Number of pages8
ISBN (Print)9781450359337
DOIs
Publication statusPublished - 2019
Publication typeA4 Article in a conference publication
EventAnnual ACM Symposium on Applied Computing - Limassol, Cyprus
Duration: 8 Apr 201912 Apr 2019

Conference

ConferenceAnnual ACM Symposium on Applied Computing
CountryCyprus
CityLimassol
Period8/04/1912/04/19

Abstract

Background: Achieving a steady stream of small releases and employing practices such as continuous deployment requires maturity in company processes. Maturity models provide one approach for companies to pinpoint areas of improvement by providing a position and hints to reflect on. Incorporating maturity models with agile software development and continuous deployment has its challenges, though. Aims: The focus of the study is in understanding the evolution of software processes towards continuous deployment in an industry organization over time when a maturity model is used as a yardstick in evaluation. Method: An embedded case study by design, the study utilizes and replicates a survey on the state of software projects in a large Finnish software company, Solita. The survey was initially conducted in 2015 with responses from 35 projects and now replicated in 2017 with responses from 43 projects. Both quantitative and qualitative approaches for survey responses are used in the analysis. Results: Maturity of software processes in the case company show improvement in deployment and in monitoring, albeit short of statistical significance. Technological advances in the application of cloud computing have likely spurred development in these areas. Capability in processes related to test automation and quality has not changed much in two years. Conclusions: Maintaining maturity in software processes requires constant attention as impressions on process quality can gradually diminish. Projects which are built on a compatible technology stack have a greater chance in achieving continuous deployment and thus being more mature. Customer preferences also make a difference in the ability to reach certain maturity levels.

ASJC Scopus subject areas

Publication forum classification

Field of science, Statistics Finland