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

Explore the episodes
Podcast
In this episode of Continuous Delivery Office Hours, Steve Fenton is joined by Octopus Deploy founder Paul Stovell to explore the hidden bottleneck in the AI productivity conversation that nobody is talking about: compliance and risk tolerance. Everyone wants code written faster, so they are turning to AI to make it happen. But the constraint […]
In this episode of Continuous Delivery Office Hours, Tony Kelly, Bob Walker, and Steve Fenton discuss some of the tangled pathways around AI, the search for efficiency and productivity, and the need to re-focus on effectiveness and outcomes. You’ll find out about the beneficiary user versus end user divergence and where asymmetry can cause bad […]
In this episode of Continuous Delivery Office Hours, Tony Kelly, Bob Walker, and Steve Fenton discuss modern multi-tenancy and how different it is today than during the SaaS revolution. Multi-tenancy has a single purpose; sharing resources between users to get higher utilization from physical infrastructure by sharing it. Originally that meant time sharing on a […]
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 […]
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 […]
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 You can also watch episodes on YouTube.
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 […]
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 You can also watch episodes on YouTube.
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 […]
