CD Office Hours

About the podcast

Continuous Delivery Office Hours is a series of conversations from long-time practitioners. They cover both theoretical and practical implications, the principles and practices, and discussions around how our instincts are misleading when it comes to getting better at software delivery.

Subscribe on your favorite platform

black and silver microphone on brown wall

Explore the episodes

Podcast

CD Office Hours Ep.6: Change approvals

In this episode of Continuous Delivery Office Hours, Tony Kelly, Bob Walker, and Steve Fenton discuss the purpose and common pitfalls of software change approvals. They argue that strict, manual change approval processes are often just a reflex to past organizational trauma and an attempt to have “humans on the hook” to blame, rather than […]

CD Office Hours Ep.5: Delivering database changes

While application code deployments have become highly automated and disciplined, database changes often remain manual, “folksy,” and prone to causing messy environment drift. Find out why databases require a uniquely cautious approach due to the severe risks of data loss and the impossibility of simple rollbacks, emphasizing the need to treat database deployments with the […]

CD Office Hours Ep.4: Mono, Micro, Mesco

Your system’s architecture can support team autonomy, independent deployability, and independent evolution of components, or it can be a sticky mess. This episode looks at whether choosing a monolith or microservices fundamentally changes the crucial properties of your architecture. Listen to find out more about: Episode details Watch the video

CD Office Hours Ep.3: Branching strategies

Your branching strategy can support Continuous Delivery, or make it an impossible goal. Teams should assess the impact of how they branch on their ability to deliver software at all times, and that means there are some branching techniques that make software delivery more like walking in the dark through a field of rakes. Listen […]

CD Office Hours Ep.2: Am I Deployable?

To ensure software is deployable, teams must shift from manual testing to automated pipelines. Automation provides immediate feedback, captures institutional knowledge, and reduces long-term costs. Strategies like the Strangler Pattern help modernize legacy code for greater reliability. Listen to find out more about: Episode map Watch the video

CD Office Hours Ep.1: Prioritizing Continuous Delivery

Tony Kelly hosts our first episode of Continuous Delivery Office Hours, with Bob Walker and Steve Fenton. In this episode of Continuous Delivery Office Hours, we ponder why prioritizing Continuous Delivery (CD) is essential for managing risk. We challenge the common instinct to reduce deployment frequency after failures, using a dentist analogy to explain how […]

The Continuous Delivery Office Hours podcast is sponsored by

Octopus Deploy