I understand. My point is that all development processes I know are based on tasks. A developer is not supposed to do (or at least isn't paid for doing) anything outside a task. So to make the reduction of technical debt happen, you need to define tasks for it in the standard tracking system as well.
I understand. My point is that all development processes I know are based on tasks. A developer is not supposed to do (or at least isn't paid for doing) anything outside a task. So to make the reduction of technical debt happen, you need to define tasks for it in the standard tracking system as well.
Yes, you need and you need to plan it as a part of the sprint/milestone/etc.
In my honest opinion, it is a bad practice from evolution/growth perspective.
Not neccessarily if a developer can create additional tasks without too much bureaucratic overhead.