<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>How to Effectively Capture a Defect in Agile environment</title>
		<description>Discuss How to Effectively Capture a Defect in Agile environment</description>
		<link>https://www.agiledevelopment.org/agile-talk/147-how-to-effectively-capture-a-defect-in-agile-environment</link>
		<lastBuildDate>Fri, 05 Jun 2026 20:41:32 +0000</lastBuildDate>
		<generator>JComments</generator>
		<atom:link href="http://www.agiledevelopment.org/component/jcomments/feed/com_content/147" rel="self" type="application/rss+xml" />
		<item>
			<title>James says:</title>
			<link>https://www.agiledevelopment.org/agile-talk/147-how-to-effectively-capture-a-defect-in-agile-environment#comment-100</link>
			<description><![CDATA[Thank you for the insightful article. It is important to understand that all documentation has a value and a cost. I often find myself wishing I had more time to provide more information, but the time to do so is never easy to find.]]></description>
			<dc:creator>James</dc:creator>
			<pubDate>Tue, 19 Feb 2013 15:49:41 +0000</pubDate>
			<guid>https://www.agiledevelopment.org/agile-talk/147-how-to-effectively-capture-a-defect-in-agile-environment#comment-100</guid>
		</item>
	</channel>
</rss>
