I agree on the timeboxing/sprints. I also think those are unfit for regular software development though. For everything else, there are many techniques that ca

I agree on the timeboxing/sprints. I also think those are unfit for regular software development though. For everything else, there are many techniques that can be used depending on what it is that you're doing. They are generally the same used on agile and XP software development. How to apply them may differ but the ideas are the same. Blue/green deployments, canary deployments, expand/contract, isolated prod-like environments, branching by abstraction are all great for reducing risk and blast radius when iterating. Test-first approaches where applicable help catch issues earlier. It takes more work and more time than big bang releases but the risk of outages can be reduced to statistical error.