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.