Enhancing software release velocity

Thumbnail Image

Files

master_Syed_Maria_2025.pdf (3.62 MB)

URL

Journal Title

Journal ISSN

Volume Title

School of Science | Master's thesis
Unless otherwise stated, all rights belong to the author. You may download, display and print this publication for Your own personal use. Commercial use is prohibited.

Authors

Date

2025-11-18

Department

Major/Subject

Computer Science

Mcode

Degree programme

Master's Programme in Computer, Communication and Information Sciences
Master's Programme in Computer, Communication and Information Sciences
Master's Programme in Computer, Communication and Information Sciences

Language

en

Pages

99

Series

Abstract

This thesis investigates critical software delivery latency at a large fintech organization, where a modern micro-application architecture was severely bottle-necked by a legacy, manual, ticketing-based approval system. This hybrid environment created an acute organizational bottleneck, imposing high coordination burdens and unpredictable delays on globally distributed feature teams. Using an Action Research (AR) methodology, the study first established a high-friction baseline, measuring the median Lead Time for Changes (LTC) at 20.2 hours. The core intervention involved replacing the mandatory manual approval gate with a fully automated, self-service deployment model integrated directly into the Continuous Integration/Continuous Delivery (CI/CD) pipeline. The intervention successfully drove significant organizational efficiency, yielding a 69% reduction in LTC, dropping the median time from 20.2 hours to 6.2 hours. Concurrently, Deployment Frequency (DF) increased by 213% (from 47 to 100 releases per week). This improvement solidified the organization's position within the DORA elite performance tier. The primary practical guidance derived from this case study is that sustained software acceleration requires prioritizing the decentralization of control over the deployment trigger. This is achieved not merely through technical automation, but by deliberately eliminating all mandatory human coordination steps via external systems (e.g., tickets), relying instead on real-time visibility tooling integrated into the developer workflow. Additionally, and more importantly, this required a complementary organizational culture shift, which involved transfer-ring accountability for production stability directly from administrative roles, such as the Program Manager, to the autonomous development teams.

Description

Supervisor

Lassenius, Casper

Thesis advisor

Dzhioev, Alexander

Keywords

software release management, release automation, continuous delivery, DevOps, software delivery, deployment notification system

Other note

Citation

Permanent link to this item

https://urn.fi/URN:NBN:fi:aalto-202512179418

Collections

[dipl] Perustieteiden korkeakoulu / SCI