The Right Amount of Technical Debt in an Agile Context
Ciolkowski, Marcus; Diebold, Philipp; Janes, Andrea; Lenarduzzi, Valentina (2025-01-11)
Ciolkowski, Marcus
Diebold, Philipp
Janes, Andrea
Lenarduzzi, Valentina
Springer
11.01.2025
Ciolkowski, M., Diebold, P., Janes, A., Lenarduzzi, V. (2025). The Right Amount of Technical Debt in an Agile Context. In: Marchesi, L., et al. Agile Processes in Software Engineering and Extreme Programming – Workshops. XP 2024. Lecture Notes in Business Information Processing, vol 524. Springer, Cham. https://doi.org/10.1007/978-3-031-72781-8_27
https://creativecommons.org/licenses/by/4.0/
© 2025 The Author(s). This chapter is licensed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits use, sharing, adaptation, distribution and reproduction in any medium or format, as long as you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license and indicate if changes were made. The images or other third party material in this chapter are included in the chapter's Creative Commons license, unless indicated otherwise in a credit line to the material. If material is not included in the chapter's Creative Commons license and your intended use is not permitted by statutory regulation or exceeds the permitted use, you will need to obtain permission directly from the copyright holder.
https://creativecommons.org/licenses/by/4.0/
© 2025 The Author(s). This chapter is licensed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits use, sharing, adaptation, distribution and reproduction in any medium or format, as long as you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license and indicate if changes were made. The images or other third party material in this chapter are included in the chapter's Creative Commons license, unless indicated otherwise in a credit line to the material. If material is not included in the chapter's Creative Commons license and your intended use is not permitted by statutory regulation or exceeds the permitted use, you will need to obtain permission directly from the copyright holder.
https://creativecommons.org/licenses/by/4.0/
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:oulu-202504172772
https://urn.fi/URN:NBN:fi:oulu-202504172772
Tiivistelmä
Abstract
Agile and technical debt management should have a symbiotic relationship, as technical debt was conceived as a metaphor (or tool) to balance the benefits of taking shortcuts for early release and user feedback with the responsibility of ‘repairing’ the effects of these trade-offs. Agile processes provide the necessary flexibility to achieve this balance. However, in reality, feature greed often takes over, making it difficult for development teams to ensure that technical debt is repaid. This paper discusses experiences and best practices to address Technical Debt in an Agile context.
Agile and technical debt management should have a symbiotic relationship, as technical debt was conceived as a metaphor (or tool) to balance the benefits of taking shortcuts for early release and user feedback with the responsibility of ‘repairing’ the effects of these trade-offs. Agile processes provide the necessary flexibility to achieve this balance. However, in reality, feature greed often takes over, making it difficult for development teams to ensure that technical debt is repaid. This paper discusses experiences and best practices to address Technical Debt in an Agile context.
Kokoelmat
- Avoin saatavuus [37693]