Technical debt is incurred when a development team delivers a business feature that is incomplete or is not a solid foundation for future enhancements e.g. future development capacity is being committed to deliver a feature today. If technical debt is not addressed, and instead additional features are built on top of the incomplete work, over time it can become more and more challenging to deliver business value. In this podcast Andy Forbes talks to Erik Ivarsson, a Managing Solution Architect with Capgemini Sweden, and Matt Prorok, a Field Service Lightning Architect with Capgemini America, about technical debt.