But, technical debt is a real thing. Making sure that refactoring/clearing debt is part of every sprint (one or two tasks per sprint, probably) is important. H

But, technical debt is a real thing. Making sure that refactoring/clearing debt is part of every sprint (one or two tasks per sprint, probably) is important. However, if benefits of refactoring are abstract, and not attached to immediate or short-term/medium term features/perf, there is a very high probability that it is not a tech debt. "Code looks better this way" - is an overrated rationale to refactor.