<?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>Quality Assurance on The Agile Techies Daily List</title>
    <link>https://agiletechies.com/tags/quality-assurance/</link>
    <description>Recent content in Quality Assurance 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>Mon, 26 May 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://agiletechies.com/tags/quality-assurance/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Defect Economy</title>
      <link>https://agiletechies.com/posts/the-defect-economy/</link>
      <pubDate>Mon, 26 May 2025 00:00:00 +0000</pubDate><author>rajesh@duggalmail.com (Raj Duggal)</author>
      <guid>https://agiletechies.com/posts/the-defect-economy/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve seen teams rewarded for finding as many defects as possible.&lt;/p&gt;
&lt;p&gt;Better that the teams finds them, rather than end-user, right?  Over time the culture and metrics rate a higher defect count as proof of the QA is doing well.&lt;/p&gt;
&lt;p&gt;Defects become a currency that some team members benefit from. The builders learn that if a high defect count isn&amp;rsquo;t a problem, then they can meet their delivery deadlines simply by announcing imperfect work as completed.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Bring QA to the Front</title>
      <link>https://agiletechies.com/posts/bring-qa-to-the-front/</link>
      <pubDate>Fri, 23 May 2025 00:00:00 +0000</pubDate><author>rajesh@duggalmail.com (Raj Duggal)</author>
      <guid>https://agiletechies.com/posts/bring-qa-to-the-front/</guid>
      <description>&lt;p&gt;Quality Assurance must stop being a back‑end gatekeeper. QA belongs at the front, providing early input to prevent errors and omissions, not just measuring and reporting them later.&lt;/p&gt;
&lt;p&gt;The team injects QA activities into planning, define acceptance criteria, and automating test execution as the features are being built.&lt;/p&gt;
&lt;p&gt;When QA focus and practices are incorporated from the start, the team can reduce rework, be met with fewer negative surprises, and deliver value at a consistent pace.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
