Abstract
Technical Debt is incurred when the agile team proactively determines that a less optimum, less efficient, or less robust solution is appropriate given constraints of time, budget, or resources. As this graphic from Martin Fowler describes, as technical debt increases, the costs and effort to continue development, or maintain an existing system, will become too high, and a “technical debt sprint” should be scheduled within a release to improve code quality.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2019 Jeff Dalton
About this chapter
Cite this chapter
Dalton, J. (2019). Technical Debt. In: Great Big Agile. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-4206-3_66
Download citation
DOI: https://doi.org/10.1007/978-1-4842-4206-3_66
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-4205-6
Online ISBN: 978-1-4842-4206-3
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books