<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ci-cd on Agile Software Development</title>
    <link>https://agilesoftdev.com/tags/ci-cd/</link>
    <description>Recent content in ci-cd on Agile Software Development</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 02 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://agilesoftdev.com/tags/ci-cd/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Preconfiguration: Solves the Setup Problem for Agile Teams Using Multiple Coding Agents</title>
      <link>https://agilesoftdev.com/preconfiguration-solves-the-setup-problem-for-agile-teams-using-multiple-coding-agents/</link>
      <pubDate>Fri, 02 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://agilesoftdev.com/preconfiguration-solves-the-setup-problem-for-agile-teams-using-multiple-coding-agents/</guid>
      <description>Every developer has lived the setup nightmare. You clone the repo, follow the README, get halfway through the steps, and something breaks. You Google the error, find three different solutions, apply the one that almost works, and spend two hours on an environment that everyone else on the team got right. Meanwhile, the new developer at the desk next to you is still stuck on step one. The setup is so fragile that nobody wants to change it, and it drifts from the reality of how the tests actually run.</description>
    </item>
    
  </channel>
</rss>
