<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Bug Management: Auto expire defects.</title>
	<atom:link href="http://digitalbrikes.com/onebrikeatatime/2009/01/21/bug-management-auto-expire-defects/feed/" rel="self" type="application/rss+xml" />
	<link>http://digitalbrikes.com/onebrikeatatime/2009/01/21/bug-management-auto-expire-defects/</link>
	<description>Notes on software development</description>
	<lastBuildDate>Tue, 08 May 2012 08:40:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Denis</title>
		<link>http://digitalbrikes.com/onebrikeatatime/2009/01/21/bug-management-auto-expire-defects/comment-page-1/#comment-969</link>
		<dc:creator>Denis</dc:creator>
		<pubDate>Sat, 14 Feb 2009 01:31:38 +0000</pubDate>
		<guid isPermaLink="false">http://digitalbrikes.com/onebrikeatatime/?p=82#comment-969</guid>
		<description>The idea behind this is to avoid wasting time going over endless lists of irrelevant bugs. The time would be better spent going over the list of new features.

Autoexpire would ensure only fresh bugs are prioritized.</description>
		<content:encoded><![CDATA[<p>The idea behind this is to avoid wasting time going over endless lists of irrelevant bugs. The time would be better spent going over the list of new features.</p>
<p>Autoexpire would ensure only fresh bugs are prioritized.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: César</title>
		<link>http://digitalbrikes.com/onebrikeatatime/2009/01/21/bug-management-auto-expire-defects/comment-page-1/#comment-962</link>
		<dc:creator>César</dc:creator>
		<pubDate>Wed, 11 Feb 2009 19:32:08 +0000</pubDate>
		<guid isPermaLink="false">http://digitalbrikes.com/onebrikeatatime/?p=82#comment-962</guid>
		<description>That&#039;s one way to do it.

Are your users involved in managing the list of bugs?

If they were the sole owners of the list, you would only care about the top items of the list, down to a threshold. The threshold is determined by
(1) the things that must be done for the health of the system (your P1s, but probably not P2s) and
(2) the capacity for bug fixing that your Product Owner has requested for the next iteration and that the team has committed to (but being at least whatever it takes to address (1))

César.</description>
		<content:encoded><![CDATA[<p>That&#8217;s one way to do it.</p>
<p>Are your users involved in managing the list of bugs?</p>
<p>If they were the sole owners of the list, you would only care about the top items of the list, down to a threshold. The threshold is determined by<br />
(1) the things that must be done for the health of the system (your P1s, but probably not P2s) and<br />
(2) the capacity for bug fixing that your Product Owner has requested for the next iteration and that the team has committed to (but being at least whatever it takes to address (1))</p>
<p>César.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

