<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="http://futureof.dev/wp-content/plugins/seriously-simple-podcasting/templates/feed-stylesheet.xsl"?><rss version="2.0"
	 xmlns:content="http://purl.org/rss/1.0/modules/content/"
	 xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	 xmlns:dc="http://purl.org/dc/elements/1.1/"
	 xmlns:atom="http://www.w3.org/2005/Atom"
	 xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	 xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	 xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	 xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"
	 xmlns:podcast="https://podcastindex.org/namespace/1.0"
	>
		<channel>
		<title>Continuous Delivery Office Hours</title>
		<atom:link href="http://futureof.dev/feed/podcast/continuous-delivery-office-hours/" rel="self" type="application/rss+xml"/>
		<link>https://futureof.dev/podcasts/continuous-delivery-office-hours/</link>
		<description>Hear about Continuous Delivery from the team at Octopus. Bob Walker, Steve Fenton, and Tony Kelly have enough combined experience in years to walk a new software version to the moon, but we know a few better ways to deliver software.</description>
		<lastBuildDate>Mon, 06 Apr 2026 11:40:03 +0000</lastBuildDate>
		<language>en-US</language>
		<copyright>© 2026 Future of Dev</copyright>
		<itunes:subtitle></itunes:subtitle>
		<itunes:author>Future of Dev</itunes:author>
		<itunes:type>episodic</itunes:type>
		<itunes:summary>Hear about Continuous Delivery from the team at Octopus. Bob Walker, Steve Fenton, and Tony Kelly have enough combined experience in years to walk a new software version to the moon, but we know a few better ways to deliver software.</itunes:summary>
		<itunes:owner>
			<itunes:name>Future of Dev</itunes:name>
		</itunes:owner>
		<itunes:explicit>false</itunes:explicit>
		<itunes:image href="https://futureof.dev/wp-content/uploads/2026/01/cd-office-hours-sq-1600.png"></itunes:image>
			<image>
				<url>https://futureof.dev/wp-content/uploads/2026/01/cd-office-hours-sq-1600.png</url>
				<title>Continuous Delivery Office Hours</title>
				<link>https://futureof.dev/podcasts/continuous-delivery-office-hours/</link>
			</image>
		<itunes:category text="Technology">
		</itunes:category>
		<googleplay:author><![CDATA[Future of Dev]]></googleplay:author>
						<googleplay:description>Hear about Continuous Delivery from the team at Octopus. Bob Walker, Steve Fenton, and Tony Kelly have enough combined experience in years to walk a new software version to the moon, but we know a few better ways to deliver software.</googleplay:description>
			<googleplay:explicit>No</googleplay:explicit>
			<googleplay:image href="https://futureof.dev/wp-content/uploads/2026/01/cd-office-hours-sq-1600.png"></googleplay:image>
			<podcast:guid>8314e951-6db8-55a4-87b7-70bc64357d11</podcast:guid>
		
		<!-- podcast_generator="SSP by Castos/3.14.4" Seriously Simple Podcasting plugin for WordPress (https://wordpress.org/plugins/seriously-simple-podcasting/) -->
		<generator>https://wordpress.org/?v=6.9.4</generator>

<item>
	<title>CD Office Hours Ep.6: Change approvals</title>
	<link>https://futureof.dev/podcast/cd-office-hours-ep-6-change-approvals/</link>
	<pubDate>Mon, 06 Apr 2026 11:40:03 +0000</pubDate>
	<dc:creator><![CDATA[Future of Dev]]></dc:creator>
	<guid isPermaLink="false">490b2b60-1c8f-5bb2-b213-2b46e5b3f2a9</guid>
	<description><![CDATA[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 &#8220;humans on the hook&#8221; to blame, rather than [&#8230;]]]></description>
	<itunes:subtitle><![CDATA[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 o]]></itunes:subtitle>
	<itunes:episodeType>full</itunes:episodeType>
	<itunes:title><![CDATA[Change approvals]]></itunes:title>
	<itunes:episode>6</itunes:episode>
	<itunes:season>1</itunes:season>
	<content:encoded><![CDATA[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 &#8220;humans on the hook&#8221; to blame, rather than [&#8230;]]]></content:encoded>
	<enclosure url="https://futureof.dev/podcast-download/153/cd-office-hours-ep-6-change-approvals.mp3" length="73219200" type="audio/mpeg"></enclosure>
	<itunes:summary><![CDATA[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 &#8220;humans on the hook&#8221; to blame, rather than [&#8230;]]]></itunes:summary>
	<itunes:image href="https://futureof.dev/wp-content/uploads/2026/04/cd-office-hours-ep6-change-approvals-cover-scaled.jpg"></itunes:image>
	<image>
		<url>https://futureof.dev/wp-content/uploads/2026/04/cd-office-hours-ep6-change-approvals-cover-scaled.jpg</url>
		<title>CD Office Hours Ep.6: Change approvals</title>
	</image>
	<itunes:explicit>false</itunes:explicit>
	<itunes:block>no</itunes:block>
	<itunes:duration>00:30:30</itunes:duration>
	<itunes:author><![CDATA[Future of Dev]]></itunes:author>	<googleplay:description><![CDATA[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 &#8220;humans on the hook&#8221; to blame, rather than [&#8230;]]]></googleplay:description>
	<googleplay:image href="https://futureof.dev/wp-content/uploads/2026/04/cd-office-hours-ep6-change-approvals-cover-scaled.jpg"></googleplay:image>
	<googleplay:explicit>No</googleplay:explicit>
	<googleplay:block>no</googleplay:block>
</item>

<item>
	<title>CD Office Hours Ep.5: Delivering database changes</title>
	<link>https://futureof.dev/podcast/cd-office-hours-ep-5-delivering-database-changes/</link>
	<pubDate>Mon, 23 Mar 2026 10:00:00 +0000</pubDate>
	<dc:creator><![CDATA[Future of Dev]]></dc:creator>
	<guid isPermaLink="false">783ef9b6-2245-5f71-ba8f-1977eebf6266</guid>
	<description><![CDATA[While application code deployments have become highly automated and disciplined, database changes often remain manual, &#8220;folksy,&#8221; 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 [&#8230;]]]></description>
	<itunes:subtitle><![CDATA[While application code deployments have become highly automated and disciplined, database changes often remain manual, &#8220;folksy,&#8221; and prone to causing messy environment drift. Find out why databases require a uniquely cautious approach due to ]]></itunes:subtitle>
	<itunes:episodeType>full</itunes:episodeType>
	<itunes:title><![CDATA[Delivering database changes]]></itunes:title>
	<itunes:episode>5</itunes:episode>
	<itunes:season>1</itunes:season>
	<content:encoded><![CDATA[While application code deployments have become highly automated and disciplined, database changes often remain manual, &#8220;folksy,&#8221; 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 [&#8230;]]]></content:encoded>
	<enclosure url="https://futureof.dev/podcast-download/136/cd-office-hours-ep-5-delivering-database-changes.mp3" length="89181120" type="audio/mpeg"></enclosure>
	<itunes:summary><![CDATA[While application code deployments have become highly automated and disciplined, database changes often remain manual, &#8220;folksy,&#8221; 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 [&#8230;]]]></itunes:summary>
	<itunes:image href="https://futureof.dev/wp-content/uploads/2026/03/cd-office-hours-ep5-delivering-database-changes-cover-scaled.jpg"></itunes:image>
	<image>
		<url>https://futureof.dev/wp-content/uploads/2026/03/cd-office-hours-ep5-delivering-database-changes-cover-scaled.jpg</url>
		<title>CD Office Hours Ep.5: Delivering database changes</title>
	</image>
	<itunes:explicit>false</itunes:explicit>
	<itunes:block>no</itunes:block>
	<itunes:duration>00:37:10</itunes:duration>
	<itunes:author><![CDATA[Future of Dev]]></itunes:author>	<googleplay:description><![CDATA[While application code deployments have become highly automated and disciplined, database changes often remain manual, &#8220;folksy,&#8221; 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 [&#8230;]]]></googleplay:description>
	<googleplay:image href="https://futureof.dev/wp-content/uploads/2026/03/cd-office-hours-ep5-delivering-database-changes-cover-scaled.jpg"></googleplay:image>
	<googleplay:explicit>No</googleplay:explicit>
	<googleplay:block>no</googleplay:block>
</item>

<item>
	<title>CD Office Hours Ep.4: Mono, Micro, Mesco</title>
	<link>https://futureof.dev/podcast/cd-office-hours-ep-4-mono-micro-mesco/</link>
	<pubDate>Mon, 02 Mar 2026 08:00:00 +0000</pubDate>
	<dc:creator><![CDATA[Future of Dev]]></dc:creator>
	<guid isPermaLink="false">86acfb72-de0c-5a56-98af-ef678b19a49a</guid>
	<description><![CDATA[Your system&#8217;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]]></description>
	<itunes:subtitle><![CDATA[Your system&#8217;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 cruci]]></itunes:subtitle>
	<content:encoded><![CDATA[Your system&#8217;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]]></content:encoded>
	<enclosure url="https://futureof.dev/podcast-download/97/cd-office-hours-ep-4-mono-micro-mesco.mp3" length="73622400" type="audio/mpeg"></enclosure>
	<itunes:summary><![CDATA[Your system&#8217;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]]></itunes:summary>
	<itunes:image href="https://futureof.dev/wp-content/uploads/2026/02/cd-office-hours-ep4-mono-micro-mesco-cover-scaled.jpg"></itunes:image>
	<image>
		<url>https://futureof.dev/wp-content/uploads/2026/02/cd-office-hours-ep4-mono-micro-mesco-cover-scaled.jpg</url>
		<title>CD Office Hours Ep.4: Mono, Micro, Mesco</title>
	</image>
	<itunes:explicit>false</itunes:explicit>
	<itunes:block>no</itunes:block>
	<itunes:duration>00:30:41</itunes:duration>
	<itunes:author><![CDATA[Future of Dev]]></itunes:author>	<googleplay:description><![CDATA[Your system&#8217;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]]></googleplay:description>
	<googleplay:image href="https://futureof.dev/wp-content/uploads/2026/02/cd-office-hours-ep4-mono-micro-mesco-cover-scaled.jpg"></googleplay:image>
	<googleplay:explicit>No</googleplay:explicit>
	<googleplay:block>no</googleplay:block>
</item>

<item>
	<title>CD Office Hours Ep.3: Branching strategies</title>
	<link>https://futureof.dev/podcast/cd-office-hours-ep-3-branching-strategies/</link>
	<pubDate>Mon, 23 Feb 2026 10:00:00 +0000</pubDate>
	<dc:creator><![CDATA[Future of Dev]]></dc:creator>
	<guid isPermaLink="false">e07820cb-adce-5203-9f92-457cb1388212</guid>
	<description><![CDATA[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 [&#8230;]]]></description>
	<itunes:subtitle><![CDATA[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 soft]]></itunes:subtitle>
	<itunes:episodeType>full</itunes:episodeType>
	<itunes:title><![CDATA[Branching Strategies]]></itunes:title>
	<itunes:episode>3</itunes:episode>
	<itunes:season>1</itunes:season>
	<content:encoded><![CDATA[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 [&#8230;]]]></content:encoded>
	<enclosure url="https://futureof.dev/podcast-download/89/cd-office-hours-ep-3-branching-strategies.mp3" length="73357440" type="audio/mpeg"></enclosure>
	<itunes:summary><![CDATA[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 [&#8230;]]]></itunes:summary>
	<itunes:image href="https://futureof.dev/wp-content/uploads/2026/02/cd-office-hours-ep3-branching-strategies-cover-scaled.jpg"></itunes:image>
	<image>
		<url>https://futureof.dev/wp-content/uploads/2026/02/cd-office-hours-ep3-branching-strategies-cover-scaled.jpg</url>
		<title>CD Office Hours Ep.3: Branching strategies</title>
	</image>
	<itunes:explicit>false</itunes:explicit>
	<itunes:block>no</itunes:block>
	<itunes:duration>00:30:34</itunes:duration>
	<itunes:author><![CDATA[Future of Dev]]></itunes:author>	<googleplay:description><![CDATA[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 [&#8230;]]]></googleplay:description>
	<googleplay:image href="https://futureof.dev/wp-content/uploads/2026/02/cd-office-hours-ep3-branching-strategies-cover-scaled.jpg"></googleplay:image>
	<googleplay:explicit>No</googleplay:explicit>
	<googleplay:block>no</googleplay:block>
</item>

<item>
	<title>CD Office Hours Ep.2: Am I Deployable?</title>
	<link>https://futureof.dev/podcast/cd-office-hours-ep-2-am-i-deployable/</link>
	<pubDate>Mon, 02 Feb 2026 19:44:56 +0000</pubDate>
	<dc:creator><![CDATA[Future of Dev]]></dc:creator>
	<guid isPermaLink="false">c7a13be5-4299-506f-a5e2-bbb1548ef6ff</guid>
	<description><![CDATA[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]]></description>
	<itunes:subtitle><![CDATA[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 leg]]></itunes:subtitle>
	<itunes:episodeType>full</itunes:episodeType>
	<itunes:title><![CDATA[Am I Deployable?]]></itunes:title>
	<itunes:episode>2</itunes:episode>
	<itunes:season>1</itunes:season>
	<content:encoded><![CDATA[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]]></content:encoded>
	<enclosure url="https://futureof.dev/podcast-download/79/cd-office-hours-ep-2-am-i-deployable.mp3" length="87933120" type="audio/mpeg"></enclosure>
	<itunes:summary><![CDATA[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]]></itunes:summary>
	<itunes:image href="https://futureof.dev/wp-content/uploads/2026/01/cd-office-hours-ep2-am-i-deployable-cover-scaled.jpg"></itunes:image>
	<image>
		<url>https://futureof.dev/wp-content/uploads/2026/01/cd-office-hours-ep2-am-i-deployable-cover-scaled.jpg</url>
		<title>CD Office Hours Ep.2: Am I Deployable?</title>
	</image>
	<itunes:explicit>false</itunes:explicit>
	<itunes:block>no</itunes:block>
	<itunes:duration>00:36:38</itunes:duration>
	<itunes:author><![CDATA[Future of Dev]]></itunes:author>	<googleplay:description><![CDATA[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]]></googleplay:description>
	<googleplay:image href="https://futureof.dev/wp-content/uploads/2026/01/cd-office-hours-ep2-am-i-deployable-cover-scaled.jpg"></googleplay:image>
	<googleplay:explicit>No</googleplay:explicit>
	<googleplay:block>no</googleplay:block>
</item>

<item>
	<title>CD Office Hours Ep.1: Prioritizing Continuous Delivery</title>
	<link>https://futureof.dev/podcast/cd-office-hours-ep-1-prioritizing-continuous-delivery/</link>
	<pubDate>Mon, 26 Jan 2026 13:00:53 +0000</pubDate>
	<dc:creator><![CDATA[Future of Dev]]></dc:creator>
	<guid isPermaLink="false">cc0a9923-b3af-5ef3-9dae-eefa7facce53</guid>
	<description><![CDATA[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 [&#8230;]]]></description>
	<itunes:subtitle><![CDATA[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 challeng]]></itunes:subtitle>
	<itunes:episodeType>full</itunes:episodeType>
	<itunes:title><![CDATA[Prioritizing Continuous Delivery]]></itunes:title>
	<itunes:episode>1</itunes:episode>
	<itunes:season>1</itunes:season>
	<content:encoded><![CDATA[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 [&#8230;]]]></content:encoded>
	<enclosure url="https://futureof.dev/podcast-download/51/cd-office-hours-ep-1-prioritizing-continuous-delivery.mp3" length="56680320" type="audio/mpeg"></enclosure>
	<itunes:summary><![CDATA[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 [&#8230;]]]></itunes:summary>
	<itunes:image href="https://futureof.dev/wp-content/uploads/2026/01/cd-office-hours-ep1-prioritizing-continuous-delivery-cover-scaled.jpg"></itunes:image>
	<image>
		<url>https://futureof.dev/wp-content/uploads/2026/01/cd-office-hours-ep1-prioritizing-continuous-delivery-cover-scaled.jpg</url>
		<title>CD Office Hours Ep.1: Prioritizing Continuous Delivery</title>
	</image>
	<itunes:explicit>false</itunes:explicit>
	<itunes:block>no</itunes:block>
	<itunes:duration>00:23:37</itunes:duration>
	<itunes:author><![CDATA[Future of Dev]]></itunes:author>	<googleplay:description><![CDATA[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 [&#8230;]]]></googleplay:description>
	<googleplay:image href="https://futureof.dev/wp-content/uploads/2026/01/cd-office-hours-ep1-prioritizing-continuous-delivery-cover-scaled.jpg"></googleplay:image>
	<googleplay:explicit>No</googleplay:explicit>
	<googleplay:block>no</googleplay:block>
</item>
	</channel>
</rss>
