I found that a good way to do this effectively is to scope the technical debt issues you want to fix (ideally all the issues you are aware of) and plan what we call a "blackout" period that is dedicated to that work alone. During the blackout period the team will not work on developing any new features and will not do any other work except emergencies; they will only work on fixing the technical debt issues in scope. You choose the blackout time to be during a period in which the team is known to be free or less occupied (for example during the first week of next month). This way it's planned that the team will be working only on those debt issues during that time. Don't forget to involve the other teams that depend on your team so that they plan whatever they may need from you either before or after your blackout period. Also note to involve your testing/quality team and make sure you have prepared all the tests so that you can check that the new code still achieves what the old code used to do.

Self

Architect

Hello - I see links to the techcareergrowth channel on Slack. How do I get access?

Thanks