<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Agile on Kuldeep Pisda</title><link>https://kdpisda.in/tag/agile/</link><description>Recent content in Agile on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 03 Dec 2025 12:55:10 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/agile/index.xml" rel="self" type="application/rss+xml"/><item><title>10 Continuous Integration Best Practices That Won't Make You Cry</title><link>https://kdpisda.in/10-continuous-integration-best-practices-that-wont-make-you-cry/</link><pubDate>Wed, 03 Dec 2025 12:55:10 +0530</pubDate><guid>https://kdpisda.in/10-continuous-integration-best-practices-that-wont-make-you-cry/</guid><description>&lt;p&gt;I once watched a startup&amp;rsquo;s entire deployment grind to a halt for a full day. The cause? A tiny, untested dependency change that snowballed into a cascade of failures. It was a classic &amp;lsquo;works on my machine&amp;rsquo; tragedy that cost them momentum and morale, a silent battle fought in the heart of their pipeline.&lt;/p&gt;
&lt;p&gt;That experience taught me a hard lesson: a Continuous Integration (CI) pipeline isn&amp;rsquo;t just an automation tool; it is the central nervous system of your engineering team. When it is healthy, you move fast and with confidence. When it is neglected, it becomes a source of constant friction, a tangled mess of slow builds, flaky tests, and deployment anxiety. This journey is about transforming that pipeline from a point of pain into a source of power.&lt;/p&gt;</description></item></channel></rss>