>> insufficient planning for future product requirements
This covers both low prioritization and procrastination, the former of which I think is what you're getting at, and the latter of which I think is what purpled_haze is talking about.
It's the difference between "we'd like to clean up this technical debt but these new features are too pressing" and "we have nothing else going on, we're going to clean up this technical debt..." and then never doing it. In my experience, the latter happens because no one ever generates a real execution plan to get it done, often because there's just no reward for doing so.
This covers both low prioritization and procrastination, the former of which I think is what you're getting at, and the latter of which I think is what purpled_haze is talking about.
It's the difference between "we'd like to clean up this technical debt but these new features are too pressing" and "we have nothing else going on, we're going to clean up this technical debt..." and then never doing it. In my experience, the latter happens because no one ever generates a real execution plan to get it done, often because there's just no reward for doing so.