>At the very least you need both dials! If you have only the one that management sets, saying how much time to spend refactoring, it will always be at 0. Manag

>At the very least you need both dials! If you have only the one that management sets, saying how much time to spend refactoring, it will always be at 0. Management decisions are usually CYA based, and leaving the dial set at 0 both exposes them and gives developers a get out of jail free card. i.e. leaving it at zero is suicide. That's the whole point of making it a trackable dial. Probably what would happen in most cases is it would fluctuate between 30% during average times and 0% during crunch times.