<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Scrum: How to deal with bugs during a Sprint?</title>
	<atom:link href="http://intovsts.net/2010/02/01/scrum-how-to-deal-with-bugs-during-a-sprint/feed/" rel="self" type="application/rss+xml" />
	<link>http://intovsts.net/2010/02/01/scrum-how-to-deal-with-bugs-during-a-sprint/</link>
	<description>blogging about the current and upcoming release(s) of Visual Studio Team System</description>
	<lastBuildDate>Wed, 25 Aug 2010 14:39:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Stijn Guillemyn</title>
		<link>http://intovsts.net/2010/02/01/scrum-how-to-deal-with-bugs-during-a-sprint/#comment-186</link>
		<dc:creator>Stijn Guillemyn</dc:creator>
		<pubDate>Tue, 02 Feb 2010 09:06:50 +0000</pubDate>
		<guid isPermaLink="false">http://intovsts.net/?p=460#comment-186</guid>
		<description>If it&#039;s a bug in production code, you should also take customer satisfaction into account.

To me the goal should always be to provide a fix within 1 business day.

This will limit the amount of overhead a bug can produce in terms of administration and follow-up actions (communication, tracking status, checking if a reported bug is a known issue, ...).

Of course, this only works if you haven&#039;t already built a backlog of open bugs which you should address in the (near) future. If you have, it might be a good idea to introduce one or more bugfix iterations where you shift your focus from adding functionality to stabilizing your product and improving the things it already does.

I guess most clients prefer a stable product with some core functionality in which that product does a great job over a product that does everything but does a poor job or where every action has an unpredictable outcome.</description>
		<content:encoded><![CDATA[<p>If it&#8217;s a bug in production code, you should also take customer satisfaction into account.</p>
<p>To me the goal should always be to provide a fix within 1 business day.</p>
<p>This will limit the amount of overhead a bug can produce in terms of administration and follow-up actions (communication, tracking status, checking if a reported bug is a known issue, &#8230;).</p>
<p>Of course, this only works if you haven&#8217;t already built a backlog of open bugs which you should address in the (near) future. If you have, it might be a good idea to introduce one or more bugfix iterations where you shift your focus from adding functionality to stabilizing your product and improving the things it already does.</p>
<p>I guess most clients prefer a stable product with some core functionality in which that product does a great job over a product that does everything but does a poor job or where every action has an unpredictable outcome.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
