Technical Debt Management Strategies in Frontend Engineering: How Prioritization Frameworks Affect Delivery Performance and Developer Morale
DOI:
https://doi.org/10.63282/3050-922X.IJERET-V6I4P127Keywords:
Technical Debt, Frontend Engineering, Software Architecture, Developer Productivity, Developer Experience, Agile Prioritization, Weighted Short-est Job First, Cost of Delay, Software MaintainabilityAbstract
Technical debt has become a significant concern in modern frontend engineering environments where rapid product development cycles often priori-tize short-term feature delivery over long-term maintainability. As frontend applications evolve to support complex user experiences and distributed architectures such as micro-frontends, teams frequently introduce architectural compromises, outdated dependencies, du-plicated components, and inefficient state management patterns. Over time, these issues accumulate and de-grade system quality, slowing development velocity and increasing cognitive load on developers. This paper investigates technical debt management strategies in frontend systems and evaluates how prioritization frameworks influence delivery performance and developer morale. The study analyzes widely adopted prioritization models including Weighted Shortest Job First (WSJF), Cost of Delay (CoD), and Impact–Effort matrices as mechanisms for integrating technical debt remediation into engineering roadmaps. Architectural diagrams illustrate a technical debt management pipeline that combines automated code analysis, technical debt registries, and backlog prioritization mechanisms. The findings demonstrate that organizations implementing structured prioritization frameworks expe-rience improved software delivery metrics, including increased deployment frequency and reduced defect rates. Additionally, proactive technical debt manage-ment improves developer morale by reducing frustration associated with legacy code and improving overall developer experience. The paper concludes by proposing a comprehensive technical debt governance architecture designed to support sustainable frontend development in large-scale engineering environments.
References
[1] Terese Besker, Antonio Martini, and Jan Bosch, “Technical Debt and Software Developer Productivity,” Journal of Systems and Software, 2018.
[2] Atsushi Noda, “Technical Debt and Developer Morale,” DX Engineering Research Report, 2023.
[3] Zhenyu Li, Paris Avgeriou, and Peng Liang, “A Systematic Mapping Study on Technical Debt and Its Management,” Journal of Systems and Software, vol. 101, pp. 193–220, 2015.
[4] Philippe Kruchten, Robert Nord, and Ipek Ozkaya, Managing Technical Debt: Reducing Friction in Software Development. Boston: Addison-Wesley Professional, 2019.
[5] Nicole Forsgren, Jez Humble, and Gene Kim, Accelerate: The Science of Lean Software and DevOps. Portland: IT Revolution Press, 2018.
[6] Don Reinertsen, The Principles of Product Development Flow: Second Generation Lean Product Development. Redondo Beach: Celeritas Publishing, 2009.
[7] David J. Anderson, Kanban: Successful Evolutionary Change for Your Technology Business. Blue Hole Press, 2010.
[8] Martin Fowler, Refactoring: Improving the Design of Existing Code, Second Edition. Addison-Wesley Professional, 2018
[9] Antonio Martini and Jan Bosch, “Architecture Technical Debt: Understanding Causes and Consequences,” IEEE Software, vol. 32, no. 4, pp. 42–49, 2015.
[10] Neil Brown, Yuanfang Cai, Yuepu Guo, Rick Kaz-man, Miryung Kim, Philippe Kruchten, Erin Lim, Alan MacCormack, Robert Nord, Ipek Ozkaya, Rohit Sangwan, Carolyn Seaman, Kevin Sullivan, and Nico Zazworka,“Managing Technical Debt in Software-Reliant Systems, “Proceedings of the Future of Software Engineering Conference, IEEE, 2010.