This is good advice, especially on the communication part. It's always tempting to use the word "rewrite" but most of the time you just want some assurance tha

This is good advice, especially on the communication part. It's always tempting to use the word "rewrite" but most of the time you just want some assurance that your code doesn't break things, and a rewrite is usually overkill. I would suggest you to add in additional time for refactoring into your new feature development. This has 2 benefits - you're not rewriting the whole project, just the parts that are relevant to what you are currently working on, and you're still pushing out features. It sounds like most of your refactoring work is in code isolation / scope management and creating tests.