<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>software delivery on Agile Software Development</title>
    <link>https://agilesoftdev.com/tags/software-delivery/</link>
    <description>Recent content in software delivery on Agile Software Development</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 02 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://agilesoftdev.com/tags/software-delivery/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Continuous Delivery Is Not a DevOps Practice — It Is an Agile Foundation</title>
      <link>https://agilesoftdev.com/continuous-delivery-is-not-a-devops-practice-it-is-an-agile-foundation/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://agilesoftdev.com/continuous-delivery-is-not-a-devops-practice-it-is-an-agile-foundation/</guid>
      <description>Continuous delivery is typically categorized as a DevOps or engineering operations practice: build pipelines, automated testing, deployment automation, infrastructure as code. This categorization is accurate but incomplete in a way that matters. Continuous delivery is also the technical prerequisite for agile development to function as intended, and teams that treat it as an infrastructure concern rather than a delivery discipline tend to develop a subtle dysfunction in their sprint practice.</description>
    </item>
    
  </channel>
</rss>
