<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Definition of Done on The Agile Techies Daily List</title>
    <link>https://agiletechies.com/tags/definition-of-done/</link>
    <description>Recent content in Definition of Done on The Agile Techies Daily List</description>
    <image>
      <title>The Agile Techies Daily List</title>
      <url>https://agiletechies.com/images/papermod-cover.png</url>
      <link>https://agiletechies.com/images/papermod-cover.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-US</language>
    <managingEditor>rajesh@duggalmail.com (Raj Duggal)</managingEditor>
    <webMaster>rajesh@duggalmail.com (Raj Duggal)</webMaster>
    <lastBuildDate>Thu, 22 May 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://agiletechies.com/tags/definition-of-done/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Acceptance Tests Feed Into the Definition Of Done</title>
      <link>https://agiletechies.com/posts/acceptance-tests-feed-into-the-definition-of-done/</link>
      <pubDate>Thu, 22 May 2025 00:00:00 +0000</pubDate><author>rajesh@duggalmail.com (Raj Duggal)</author>
      <guid>https://agiletechies.com/posts/acceptance-tests-feed-into-the-definition-of-done/</guid>
      <description>&lt;p&gt;Each user story should have at least one acceptance test. The tests are drafted by these business (with support from the BAs and QA) they describe the behavior they expect to in the application when the story is done. The builders work on automating these tests where practical.&lt;/p&gt;
&lt;p&gt;As the builders and the business converge and gain clarity on what they&amp;rsquo;re agreeing to deliver with a story they start to build and automate the acceptance tests. These tests are integrated into the continuous build.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
