Keeping it manageable.
WHAT PREVENTS ACCUMULATION
Automated tests, so change is safe Code review, catching problems early Continuous refactoring A definition of done that is enforced Automated checks in the pipeline Updating dependencies routinely
WHY DEPENDENCIES SPECIFICALLY
Falling behind makes upgrading progressively harder, until it becomes a project.
WHAT TO DO ROUTINELY
Apply updates, in small regular steps.
WHAT ELSE ACCUMULATES SILENTLY
Unused code Configuration for cases that no longer exist Feature flags never removed Tests nobody maintains
WHAT TO DO ABOUT THOSE
Delete them.
WHY DELETION IS UNDERRATED
Code that does not exist has no defects and no cost.
WHAT TO ESTABLISH
That improving code is normal work, not a separate activity requiring permission.
WHAT CULTURE MATTERS
Whether people feel able to say something is becoming difficult.
WHAT TO WATCH FOR
Estimates in one area consistently exceeding expectation.
WHAT THAT INDICATES
Debt, before anyone has named it.
