Change search
Link to record
Permanent link

Direct link
Publications (10 of 27) Show all publications
Zabardast, E., Paudel, B. & Gonzalez-Huerta, J. (2026). Architecture Degradation at Scale: Challenges and Insights from Practice. In: Scanniello G., Romano S., Francese R., Lenarduzzi V., Vegas S. (Ed.), Product-Focused Software Process Improvement: 26th International Conference, PROFES 2025, Salerno, Italy, December 1–3, 2025, Proceedings. Paper presented at 26th International Conference on Product-Focused Software Process Improvement, PROFES 2025, Salerno, Dec 1-3, 2025 (pp. 451-460). Springer Science+Business Media B.V.
Open this publication in new window or tab >>Architecture Degradation at Scale: Challenges and Insights from Practice
2026 (English)In: Product-Focused Software Process Improvement: 26th International Conference, PROFES 2025, Salerno, Italy, December 1–3, 2025, Proceedings / [ed] Scanniello G., Romano S., Francese R., Lenarduzzi V., Vegas S., Springer Science+Business Media B.V., 2026, p. 451-460Conference paper, Published paper (Refereed)
Abstract [en]

Large-scale software systems often experience architectural degradation, affecting maintainability, scalability, and quality. To investigate this, we conducted focus groups with senior practitioners across three large organizations. Our analysis revealed four core challenge areas: managing dependencies, ownership and organizational barriers, balancing agility with stability and cost, as well as documentation drift. These findings offer practical insights for mitigating architectural degradation in complex environments. 

Place, publisher, year, edition, pages
Springer Science+Business Media B.V., 2026
Series
Lecture Notes in Computer Science, ISSN 0302-9743 ; 16361
Keywords
Architecture Degradation, Architecture Erosion, Challenges, Insights, Technical Debt, Degradation, Software engineering, Challenge, Focus groups, Four-core, Insight, Large organizations, Large-scale software systems, Organizational barriers, Technical debts, Architecture
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-28988 (URN)10.1007/978-3-032-12089-2_30 (DOI)001718768800030 ()2-s2.0-105023325552 (Scopus ID)9783032120885 (ISBN)
Conference
26th International Conference on Product-Focused Software Process Improvement, PROFES 2025, Salerno, Dec 1-3, 2025
Funder
Knowledge Foundation, 20180010
Available from: 2025-12-12 Created: 2025-12-12 Last updated: 2026-06-25Bibliographically approved
Paudel, B., Gonzalez-Huerta, J. & Zabardast, E. (2026). Exploring the evolution of technical debt in monolithic and hybrid microservice architecture: An industrial case study. Journal of Systems and Software, 237, Article ID 112831.
Open this publication in new window or tab >>Exploring the evolution of technical debt in monolithic and hybrid microservice architecture: An industrial case study
2026 (English)In: Journal of Systems and Software, ISSN 0164-1212, E-ISSN 1873-1228, Vol. 237, article id 112831Article in journal (Refereed) Published
Abstract [en]

Organizations often migrate monolithic architectures to microservices based on ad hoc data, expert opinions, or industry trends without assessing their specific context and needs. Such transitions tend to coincide with increased architectural complexity and technical debt (TD), making it crucial to understand how TD evolves over time in industrial settings to manage it effectively. This observational study explores the evolution of technical debt density (TDD) in a single software product consisting of both monolithic and microservice architectures at a Swedish fintech company, without aiming to establish causality between architectural styles and TDD trends. We further investigate TDD trends across various microservice size categories, team types, and the relationship between size and TDD. We analyzed SonarQube TD data collected from one monolith and 78 microservices from August 2022 to December 2024, and conducted semi-structured interviews with practitioners (a development manager, a product owner, and a lead developer) to validate and contextualize the quantitative findings. Our results show that, in this case, the monolithic system exhibits a decreasing TDD trend over time despite continued growth in size, while a gradual increase in TDD is observed across microservices. Furthermore, TDD trends appear inconsistent among small microservices, more consistently growing in medium-sized microservices, and comparatively stable in larger services. Differences in TDD trends are observed across services owned by platform teams and product teams. Overall, the findings from this specific case suggest that TDD evolves differently in monolith and microservices, highlighting the importance of continuous monitoring and context-aware interpretation of TDD trends in practice. 

Place, publisher, year, edition, pages
Elsevier, 2026
Keywords
Case study, Microservices, Monolith, Software architecture, Technical debt, Architectural design, Case-studies, Expert opinion, Industrial case study, Industrial settings, Industry trends, Microservice, Monolithic architecture, Monolithics, Technical debts
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-29433 (URN)10.1016/j.jss.2026.112831 (DOI)001730374800001 ()2-s2.0-105033743010 (Scopus ID)
Funder
Knowledge Foundation, 20180010
Available from: 2026-04-17 Created: 2026-04-17 Last updated: 2026-06-25Bibliographically approved
Salin, H., Klotins, E. & Zabardast, E. (2026). Hindrances and Strengths in Software Delivery: Insights from a Developer Experience Study at the Swedish Transport Administration. In: Scanniello G., Romano S., Francese R., Lenarduzzi V., Vegas S. (Ed.), Product-Focused Software Process Improvement. Industry, Doctoral-Symposium, Tutorial, and Workshop Papers: 26th International Conference, PROFES 2025, Salerno, Italy, December 1–3, 2025, Proceedings. Paper presented at 26th International Conference on Product-Focused Software Process Improvement, PROFES 2025, Salerno, Dec 1-3, 2025 (pp. 120-135). Springer Science+Business Media B.V.
Open this publication in new window or tab >>Hindrances and Strengths in Software Delivery: Insights from a Developer Experience Study at the Swedish Transport Administration
2026 (English)In: Product-Focused Software Process Improvement. Industry, Doctoral-Symposium, Tutorial, and Workshop Papers: 26th International Conference, PROFES 2025, Salerno, Italy, December 1–3, 2025, Proceedings / [ed] Scanniello G., Romano S., Francese R., Lenarduzzi V., Vegas S., Springer Science+Business Media B.V., 2026, p. 120-135Conference paper, Published paper (Refereed)
Abstract [en]

Developer Experience (DevEx) refers to the overall experience of software developers when interacting with tools, processes, and organizational environments. This paper reports on a DevEx survey conducted within the ICT division of the Swedish Transport Administration (STA), one of the largest software development organizations in the Swedish public sector. The survey, completed by 98 out of 122 invited software engineers, included both quantitative and qualitative data. The initial results show strong (positive) scores in cultural factors, skills and competence, perceived responsibility and accountability, indicating a collaborative and supportive work environment. In contrast, the most frequently reported hindrances were meetings, context switching and inefficient work practices. Along with the analysis our study presents practitioner-oriented recommendations and lessons learned when conducting similar DevEx initiatives. 

Place, publisher, year, edition, pages
Springer Science+Business Media B.V., 2026
Series
Lecture Notes in Computer Science, ISSN 0302-9743 ; 16362
Keywords
Developer Experience, DevEx, Public Sector, Software Development, Distributed computer systems, Cultural factors, Organisational, Qualitative data, Quantitative data, Software developer, Software development organizations, Swedishs, Software design
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-28986 (URN)10.1007/978-3-032-12092-2_8 (DOI)001718774400008 ()2-s2.0-105023591499 (Scopus ID)9783032120915 (ISBN)
Conference
26th International Conference on Product-Focused Software Process Improvement, PROFES 2025, Salerno, Dec 1-3, 2025
Available from: 2025-12-12 Created: 2025-12-12 Last updated: 2026-04-17Bibliographically approved
Kosenkov, O., Zabardast, E., Fucci, D., Mendez, D. & Unterkalmsteiner, M. (2026). Privacy by design: Aligning GDPR and software engineering specifications with a requirements engineering approach. Information and Software Technology, 190, Article ID 107946.
Open this publication in new window or tab >>Privacy by design: Aligning GDPR and software engineering specifications with a requirements engineering approach
Show others...
2026 (English)In: Information and Software Technology, ISSN 0950-5849, E-ISSN 1873-6025, Vol. 190, article id 107946Article in journal (Refereed) Published
Abstract [en]

Context: Consistent requirements and system specifications are essential for the compliance of software systems towards the General Data Protection Regulation (GDPR). Both artefacts need to be "grounded" in the original text and conjointly assure the achievement of privacy by design (PbD).

Objectives: There is little understanding of the perspectives of practitioners on specification objectives and goals to address PbD. Existing approaches to GDPR and PbD do not account for the complex intersection between problem and solution space expressed in GDPR. In this study we explore the demand for conjoint requirements and system specification for PbD and suggest an initial version of an approach to address this demand.

Methods: We reviewed existing secondary and related primary studies on GDPR compliance and conducted interviews with practitioners to (1) investigate the state-of-practice in requirements and system specifications for GDPR compliance and (2) understand the underlying specification objectives and goals (e.g., traceability). We developed and evaluated an initial version of an approach for requirements and systems specification for PbD, and evaluated it against the specification objectives.

Results: The relationship between problem and solution space, as expressed in GDPR, is instrumental in supporting PbD. We demonstrate how our approach, based on the modeling GDPR content with original legal concepts, contributes to specification objectives of capturing legal knowledge, supporting specification transparency for roles involved, and traceability.

Conclusion: In addition to assuring traceability, GDPR demands need to be addressed throughout different levels of abstraction in the engineering lifecycle to achieve PbD. Legal knowledge specified in the GDPR text should be captured in specifications to address the demands of different stakeholders and ensure compliance. While our results confirm the suitability of our approach to address practical needs, we also revealed specific needs for the future effective operationalization of our suggested approach.

Place, publisher, year, edition, pages
Elsevier, 2026
Keywords
Regulatory requirements engineering, Software architecture, Privacy by design, Privacy engineering, Empirical software engineering
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-28951 (URN)10.1016/j.infsof.2025.107946 (DOI)001616037200001 ()2-s2.0-105030099379 (Scopus ID)
Available from: 2025-12-01 Created: 2025-12-01 Last updated: 2026-10-28Bibliographically approved
Paudel, B., Gonzalez-Huerta, J. & Zabardast, E. (2026). Temporal Evolution of Architectural Complexity and Technical Debt in Microservices: An Exploratory Case Study. In: Scanniello G., Romano S., Francese R., Lenarduzzi V., Vegas S. (Ed.), Product-Focused Software Process Improvement: 26th International Conference, PROFES 2025, Salerno, Italy, December 1–3, 2025, Proceedings. Paper presented at 26th International Conference on Product-Focused Software Process Improvement, PROFES 2025, Salerno, Dec 1-3, 2025 (pp. 285-302). Springer Science+Business Media B.V.
Open this publication in new window or tab >>Temporal Evolution of Architectural Complexity and Technical Debt in Microservices: An Exploratory Case Study
2026 (English)In: Product-Focused Software Process Improvement: 26th International Conference, PROFES 2025, Salerno, Italy, December 1–3, 2025, Proceedings / [ed] Scanniello G., Romano S., Francese R., Lenarduzzi V., Vegas S., Springer Science+Business Media B.V., 2026, p. 285-302Conference paper, Published paper (Refereed)
Abstract [en]

Over the last decade, software organizations have increasingly adopted microservices to effectively deal with evolving software systems, frequent demands for new features, and changing technologies. However, microservices are not a silver bullet; their success depends on the specific context and needs of each organization. Therefore, tracking the evolution of architectural complexity indicators is crucial for effective architectural governance and decision-making. In this paper, we explore the relationship between architectural complexity indicators and their evolution, specifically declared dependencies, API endpoints, inter-service communications, size, and technical debt. We used the static source code analysis methods along with SonarQube to measure architectural complexity, collecting data on all indicators over the past two and a half years. Our findings indicate that architectural complexity consistently grows, even within microservices. Most importantly, these indicators co-evolve, making the overall architecture more complicated than expected. Additionally, all complexity indicators grow rapidly when services are small and still evolving. The insights gained from this study can assist organizations in effectively managing their microservices, highlighting when they might be most prone to architectural degradation. 

Place, publisher, year, edition, pages
Springer Science+Business Media B.V., 2026
Series
Lecture Notes in Computer Science, ISSN 0302-9743 ; 16361
Keywords
Architectural Complexity, Complexity Evolution, Industrial Case Study, Microservices Architecture, Technical Debt, Architecture, Complexity indicators, Exploratory case studies, Microservice architecture, Software organization, Software-systems, Technical debts, Temporal evolution, Computer software
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-28987 (URN)10.1007/978-3-032-12089-2_18 (DOI)001718768800018 ()2-s2.0-105023329652 (Scopus ID)9783032120885 (ISBN)
Conference
26th International Conference on Product-Focused Software Process Improvement, PROFES 2025, Salerno, Dec 1-3, 2025
Funder
Knowledge Foundation, 20180010
Available from: 2025-12-12 Created: 2025-12-12 Last updated: 2026-06-25Bibliographically approved
Zabardast, E., Paudel, B. & Gonzalez-Huerta, J. (2026). The Dependency Black Hole. In: Proceedings - 2026 IEEE 23rd International Conference on Software Architecture Companion, ICSA-C 2026: . Paper presented at 23rd IEEE International Conference on Software Architecture Companion, ICSA-C 2026, Amsterdam, June 22-26, 2026 (pp. 174-178). Institute of Electrical and Electronics Engineers (IEEE)
Open this publication in new window or tab >>The Dependency Black Hole
2026 (English)In: Proceedings - 2026 IEEE 23rd International Conference on Software Architecture Companion, ICSA-C 2026, Institute of Electrical and Electronics Engineers (IEEE), 2026, p. 174-178Conference paper, Published paper (Refereed)
Abstract [en]

Microservice architectures promise independent evolution through loose coupling, yet large systems often exhibit strong dependency concentration around a small set of services. In an exploratory industrial case study of a product composed of 267 microservices, we triangulated multiple dependency signals - compile-time, run-time, and task dependencies - and iteratively validated our interpretations with practitioners. We observed a recurring macro-structure in the dependency network that resembles a black hole: a dense core of dependency magnets, a transitional region of services increasingly entangled with the core, and an outer region of lightly connected services. Based on these observations, we propose the dependency black hole theory, mapping the network to the black hole anatomy of a singularity, an event horizon, and an accretion disk, and formulating three hypotheses about how dependency concentration emerges and evolves at scale. The theory provides an explanatory lens for reasoning about dependency growth, identifying services at risk of becoming dependency magnets, and motivating governance interventions. We outline practical implications and directions for longitudinal and multi-case validation. 

Place, publisher, year, edition, pages
Institute of Electrical and Electronics Engineers (IEEE), 2026
Keywords
architectural dependency, dependency, microservice architecture, theory building, Architecture, Black holes, Gravitation, Network architecture, Independent evolutions, Industrial case study, Large system, Loose couplings, Multiple dependencies, Hole concentration
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-30473 (URN)10.1109/ICSA-C68850.2026.00044 (DOI)2-s2.0-105048450623 (Scopus ID)9798331557409 (ISBN)
Conference
23rd IEEE International Conference on Software Architecture Companion, ICSA-C 2026, Amsterdam, June 22-26, 2026
Available from: 2026-09-14 Created: 2026-09-14 Last updated: 2026-09-17Bibliographically approved
Kosenkov, O., Zabardast, E., Fischbach, J., Gorschek, T. & Mendez, D. (2026). Towards a Goal-Centric Assessment of Requirements Engineering Methods for Privacy by Design. In: Renata Guizzardi, João Araújo (Ed.), Requirements Engineering: Foundation for Software Quality, REFSQ 2026. Paper presented at 32nd International Working Conference on Requirements Engineering: Foundation for Software Quality, REFSQ 2026, Poznan, March 23-26, 2026 (pp. 207-216). Springer Science+Business Media B.V.
Open this publication in new window or tab >>Towards a Goal-Centric Assessment of Requirements Engineering Methods for Privacy by Design
Show others...
2026 (English)In: Requirements Engineering: Foundation for Software Quality, REFSQ 2026 / [ed] Renata Guizzardi, João Araújo, Springer Science+Business Media B.V., 2026, p. 207-216Conference paper, Published paper (Refereed)
Abstract [en]

Implementing privacy by design (PbD) according to the General Data Protection Regulation (GDPR) is met with a growing number of requirements engineering (RE) approaches. However, the question of which RE method for PbD fits best the goals of organisations remains a challenge. We report our endeavor to close this gap by synthesizing a goal-centric approach for PbD methods assessment. We used literature review, interviews, and validation with practitioners to achieve the goal of our study. As practitioners do not approach PbD systematically, we suggest that RE methods for PbD should be assessed against organisational goals, rather than process characteristics only. We hope that, when further developed, the goal-centric approach could support the development, selection, and tailoring of RE practices for PbD. 

Place, publisher, year, edition, pages
Springer Science+Business Media B.V., 2026
Series
Lecture Notes in Computer Science, ISSN 0302-9743 ; 16497
Keywords
empirical software engineering, privacy by design, privacy engineering, requirements engineering, software compliance, Data privacy, Design, Software engineering, Design method, Engineering methods, General data protection regulations, Literature reviews, Method assessment, Organizational goals, Privacy engineerings, Requirement engineering
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-29456 (URN)10.1007/978-3-032-21423-2_14 (DOI)001763234000014 ()2-s2.0-105035231116 (Scopus ID)9783032214225 (ISBN)
Conference
32nd International Working Conference on Requirements Engineering: Foundation for Software Quality, REFSQ 2026, Poznan, March 23-26, 2026
Available from: 2026-04-27 Created: 2026-04-27 Last updated: 2026-10-28Bibliographically approved
Gonzalez-Huerta, J. & Zabardast, E. (2026). Towards Understanding Team Congestion in Large-Scale Software Development. In: Scanniello G., Romano S., Francese R., Lenarduzzi V., Vegas S. (Ed.), Product-Focused Software Process Improvement: 26th International Conference, PROFES 2025, Salerno, Italy, December 1–3, 2025, Proceedings. Paper presented at 26th International Conference on Product-Focused Software Process Improvement, PROFES 2025, Salerno, Dec 1-3, 2025 (pp. 353-368). Springer Science+Business Media B.V.
Open this publication in new window or tab >>Towards Understanding Team Congestion in Large-Scale Software Development
2026 (English)In: Product-Focused Software Process Improvement: 26th International Conference, PROFES 2025, Salerno, Italy, December 1–3, 2025, Proceedings / [ed] Scanniello G., Romano S., Francese R., Lenarduzzi V., Vegas S., Springer Science+Business Media B.V., 2026, p. 353-368Conference paper, Published paper (Refereed)
Abstract [en]

Background: Software Development organisations tend to organise the development of software-intensive products and services as a constellation of components meant to be developed and maintained by independent, autonomous teams. However, the maintenance and evolution of said products and services require team collaboration and coordination. This collaboration and coordination overhead piles on top of teams’ workload, often hindering teams’ throughput and lead time.

Objectives: This paper aims to discuss how the use of pull request data can help identify congested teams when the arrival of new tasks exceeds the team’s ability to close them. To do so, we have conducted an empirical study in a software development organisation developing a large-scale product, to try to characterise congested teams and the characteristics of the code reviews they are involved in.

Method: We have conducted a case study to start exploring how code review data can help us model team congestion, and understand whether the features of the code-review network, or the team type (platform vs product), can have a major impact on team congestion.

Results: The results show that teams seem to experience varying levels of congestion based on pull request activity, with some indicating potential congestion. However, increased PR accumulation did not consistently lead to longer lead times, as seen in some teams where high PR backlogs did not significantly impact delivery cadence.

Conclusions: Our findings suggest that while PR data can indicate potential congestion, its impact on lead time varies across teams. Both technical factors and unobserved contextual elements shape congestion. Deeper insights require combining repository metrics with qualitative inputs. 

Place, publisher, year, edition, pages
Springer Science+Business Media B.V., 2026
Series
Lecture Notes in Computer Science, ISSN 0302-9743 ; 16361
Keywords
Case Study, Code-Review Data Analysis, Team Congestion, Team Coordination, Codes (symbols), Data reduction, Human resource management, Traffic congestion, Case-studies, Code review, Code-review data analyze, Large-scales, Leadtime, Product and services, Software development organizations, Team collaboration, Software design
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-28991 (URN)10.1007/978-3-032-12089-2_22 (DOI)001718768800022 ()2-s2.0-105023305765 (Scopus ID)9783032120885 (ISBN)
Conference
26th International Conference on Product-Focused Software Process Improvement, PROFES 2025, Salerno, Dec 1-3, 2025
Funder
Knowledge Foundation, 20180010
Available from: 2025-12-12 Created: 2025-12-12 Last updated: 2026-04-17Bibliographically approved
Zabardast, E., Vieira, T. & Gorschek, T. (2025). A 3-Layer Agentic Model for Nonfunctional Requirements in Software Engineering. In: Proceedings - 2025 40th IEEE/ACM International Conference on Automated Software Engineering Workshops, ASEW 2025: . Paper presented at 40th IEEE/ACM International Conference on Automated Software Engineering Workshops, ASEW 2025, Seoul, Nov 16-20, 2025 (pp. 51-57). Institute of Electrical and Electronics Engineers (IEEE)
Open this publication in new window or tab >>A 3-Layer Agentic Model for Nonfunctional Requirements in Software Engineering
2025 (English)In: Proceedings - 2025 40th IEEE/ACM International Conference on Automated Software Engineering Workshops, ASEW 2025, Institute of Electrical and Electronics Engineers (IEEE), 2025, p. 51-57Conference paper, Published paper (Refereed)
Abstract [en]

Modern software-intensive systems must address a wide range of nonfunctional requirements (NFRs) - such as security, compliance, and maintainability - that are critical for the long-term success of the system. With the rise of large-language-model-based agents, software engineering is entering an 'agentic' era where AI components are not only tools but collaborators in development processes. However, leveraging these agents introduces dual challenges: ensuring that AI components themselves meet quality standards (e.g., compliance, security, maintainability), and harnessing AI effectively to support systemlevel NFR assurance. Our perspective explicitly spans both SE4AI, where AI components such as agents are engineered and subjected to quality assurance and AI4SE, where AI agents support the engineering of software-intensive systems. While these are conceptually distinct, our model addresses both in a unified way. This position paper introduces a conceptual, domain-agnostic three-layer model - comprising Data, Agent, and Perspective layers - for systematically embedding AI agents into NFR assurance across the software lifecycle. The model explicitly captures two complementary viewpoints: Quality for AI (ensuring AI agents are trustworthy and maintainable) and AI for Quality (using agents to support system NFRs). Through illustrative examples in compliance, security, and maintainability, the paper demonstrates how this model can guide researchers and practitioners in designing agent-based approaches to software quality. We argue that this model not only clarifies the dual roles of AI in software engineering but also provides a foundation for responsible, scalable, and effective integration of AI into NFR assurance.

Place, publisher, year, edition, pages
Institute of Electrical and Electronics Engineers (IEEE), 2025
Keywords
AI Agents in Software Engineering, Nonfunctional Requirements (NFRs), Software Quality Assurance, Artificial intelligence, Autonomous agents, Computer software selection and evaluation, Life cycle, Maintainability, Requirements engineering, Software quality, Agent software, AI agent in software engineering, Development process, Language model, Model-based OPC, Non-functional requirements, Nonfunctional requirement, Security compliance, Software intensive systems, Quality assurance
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-29411 (URN)10.1109/ASEW67777.2025.00020 (DOI)001795671300010 ()2-s2.0-105033684669 (Scopus ID)9798331585037 (ISBN)
Conference
40th IEEE/ACM International Conference on Automated Software Engineering Workshops, ASEW 2025, Seoul, Nov 16-20, 2025
Funder
Knowledge Foundation, 20180010
Available from: 2026-04-17 Created: 2026-04-17 Last updated: 2026-08-11Bibliographically approved
Paudel, B., Gonzalez-Huerta, J., Zabardast, E. & Klotins, E. (2025). Exploring the Relationship between Technical Debt and Lead Time: An Industrial Case Study. In: Proceedings - 2025 IEEE International Conference on Software Analysis, Evolution and Reengineering, SANER 2025: . Paper presented at 32nd IEEE International Conference on Software Analysis, Evolution and Reengineering, SANER 2025, Monteral, March, 4-7, 2025 (pp. 693-703). Institute of Electrical and Electronics Engineers (IEEE)
Open this publication in new window or tab >>Exploring the Relationship between Technical Debt and Lead Time: An Industrial Case Study
2025 (English)In: Proceedings - 2025 IEEE International Conference on Software Analysis, Evolution and Reengineering, SANER 2025, Institute of Electrical and Electronics Engineers (IEEE), 2025, p. 693-703Conference paper, Published paper (Refereed)
Abstract [en]

Background: Software companies must balance fast delivery and quality, a trade-off that often introduces technical debt and wastes developer's time. Technical debt tends to increase as software evolves, which is assumed to slow down development and maintenance activities. However, the potential relationship between technical debt and lead time lacks empirical evidence.

Objective: This paper reports an empirical study to explore the potential relationship between technical debt and lead time in resolving Jira tickets. We further aim to measure the extent to which technical debt can explain the variation in lead time.

Method: We conducted an industrial case study to explore this relationship in six components, each of which was analyzed individually. Technical debt was measured using SonarQube and normalized with the component's size. Lead times to resolve Jira tickets were collected from Jira and averaged monthly.

Results: The study found little to no correlation between technical debt and lead time to resolve Jira tickets in five components, with technical debt explaining a variation in lead time ranging from 0% to 41%. However, it is less than 30% in most of the components.

Conclusion: Technical debt alone does not fully explain the variation in lead time. There should be some other confounding variables (e.g., size and complexity of the changes, number of teams involved, priorities, component ownership) affecting lead time or a residual effect, i.e., interest, that might manifest later. Further investigation into those confounding variables is essential. 

Place, publisher, year, edition, pages
Institute of Electrical and Electronics Engineers (IEEE), 2025
Keywords
Case Study, Industrial Study, Lead Time, Technical Debt, Computer software maintenance, Software design, Software quality, Case-studies, Development activity, Empirical studies, Industrial case study, Leadtime, Maintenance activity, Software company, Technical debts, Trade off, Industrial research
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-28084 (URN)10.1109/SANER64311.2025.00071 (DOI)001506888600063 ()2-s2.0-105007291171 (Scopus ID)9798331535100 (ISBN)
Conference
32nd IEEE International Conference on Software Analysis, Evolution and Reengineering, SANER 2025, Monteral, March, 4-7, 2025
Funder
Knowledge Foundation, 20180010
Available from: 2025-06-13 Created: 2025-06-13 Last updated: 2026-06-25Bibliographically approved
Organisations
Identifiers
ORCID iD: ORCID iD iconorcid.org/0000-0002-1729-5154

Search in DiVA

Show all publications