Although outwardly calm, internally you break into a cold sweat, thinking of all the changes they’ve just dropped into your lap. Your gut clenches, thinking about the explosion of possible side effects those changes will have. Since this is a non-TDD environment, regressions can only be detected manually, adding days to the QA testing schedule. As a slight silver lining, you do have some tests, but they’re a combination of low-value unit tests and slow-running integration tests, so they will be generally unhelpful in this endeavor.
The more pressing issue, however, is that the existing codebase was written sloppily. The team ended up leveraging many shortcuts like tightly-coupled classes and lack of dependency injection. Because of this coupling, removing the feature will have far-ranging effects on the codebase, putting the release at risk.