Agile taught me about refactoring but in reality I get less opportunity to refactor bad code than I've had under Waterfall-type process. My understanding of our

Agile taught me about refactoring but in reality I get less opportunity to refactor bad code than I've had under Waterfall-type process. My understanding of our evolution into Agile has always been like: 1. Big Ball of Mud: work without a plan 2. Waterfall and alike: make a very elaborate plan and stick to it 3. Agile: work without a plan, but promptly refactor issues caused by lack of foresight Waterfall worked well but is too slow to respond to change, so Agile replaces one-off planning with iterative refining. So far, great idea. However, if the backlog is never short of business requests, and business requests are always higher priority than refactoring, then when will refactoring ever be done? If we don't have architects anymore, but also don't designate time to refactor, we are de-facto doing Big Ball of Mud with stand-ups.