Isn't the classic answer to take urgent tickets and allow that to show up in decreased velocity? I have never worked anywhere, including using scrum, where I c

Isn't the classic answer to take urgent tickets and allow that to show up in decreased velocity? I have never worked anywhere, including using scrum, where I could avoid incoming issues for 2 weeks at a time. At the end of the day, better systems, better code, less technical debt means less support. Issues with previous work might indicate a false velocity of the past, releasing low quality. There are long term maintenance exceptions that happen to all code bases, that have nothing to do with quality, like supporting new platforms or unpredictable platform changes, those can go in as backlog tasks. The real question is what you are using "velocity" for? Is it to help get a feel for work you can complete, or is it a metric to be judged by management to evaluate you?