Identifying Critical Dependencies in Large-Scale Continuous Software Engineering

TL;DR

This paper investigates critical dependencies that disrupt large-scale continuous software engineering (CSE). It uses a qualitative study of 17 semi-structured interviews across two Nordic fintechs to identify where delays originate, finding that bottlenecks most often occur at the interfaces between software teams and support functions or external entities, rather than inside development teams. The authors link these findings to coordination theory and existing challenges in large-scale agile, and discuss practical implications such as aligning cadences and modernizing core systems. The work aims to inform more effective coordination mechanisms and set the stage for broader, data-driven analysis across organizations.

Abstract

Continuous Software Engineering (CSE) is widely adopted in the industry, integrating practices such as Continuous Integration and Continuous Deployment (CI/CD). Beyond technical aspects, CSE also encompasses business activities like continuous planning, budgeting, and operational processes. Coordinating these activities in large-scale product development involves multiple stakeholders, increasing complexity. This study aims to address this complexity by identifying and analyzing critical dependencies in large-scale CSE. Based on 17 semi-structured interviews conducted at two Nordic fintech companies, our preliminary findings indicate that dependencies between software teams and support functions, as well as between software teams and external entities, are the primary sources of delays and bottlenecks. As a next step, we plan to further refine our understanding of critical dependencies in large-scale CSE and explore coordination mechanisms that can better support software development teams in managing these challenges.