<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>process on Agile Software Development</title>
    <link>https://agilesoftdev.com/tags/process/</link>
    <description>Recent content in process 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/process/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Definition of Done Needs to Account for How the Code Was Built</title>
      <link>https://agilesoftdev.com/the-definition-of-done-needs-to-account-for-how-the-code-was-built/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://agilesoftdev.com/the-definition-of-done-needs-to-account-for-how-the-code-was-built/</guid>
      <description>The definition of done is one of the more underrated concepts in agile practice. A shared, explicit, team-level agreement on what it means for a story to be complete is the mechanism that prevents the slow accumulation of almost-done work that eventually freezes a sprint. Without it, done means different things to different people, and the gap is always paid for later.
AI-assisted development introduces a new category of questions that most teams&amp;rsquo; definitions of done do not yet address.</description>
    </item>
    
  </channel>
</rss>
