We often think about speed and danger as being closely related, but we now have empirical proof that faster, smaller releases tend to cause fewer outages and less downtime for our software systems. You can use that understanding to build systems that allow for the fallibility of humans and systems.

Continuous delivery requires that we’re able to deploy broken code into production without negatively affecting anyone. In a conversation with Mark Tranter, Adrian explains how to adopt this continuous delivery mind-set within your teams. You’ll learn what makes speed safer, how teams can support each other with successful failures, and why we hold to superstitions about control when we have proof to the contrary.

Join in if you’re struggling with the tension between quality, speed, and accuracy. You’ll leave with a new perspective on how small and fast a change can be—and how allowing change makes teams healthier!