<?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: What should a good iteration contain</title>
	<atom:link href="http://pathfindersoftware.com/2009/07/what-should-a-good-iteration-contain/feed/" rel="self" type="application/rss+xml" />
	<link>http://pathfindersoftware.com/2009/07/what-should-a-good-iteration-contain/</link>
	<description>The Fastest Way to Launch Successful Software</description>
	<lastBuildDate>Thu, 19 Jan 2012 16:36:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Lucas Húngaro</title>
		<link>http://pathfindersoftware.com/2009/07/what-should-a-good-iteration-contain/#comment-9665</link>
		<dc:creator>Lucas Húngaro</dc:creator>
		<pubDate>Sat, 18 Jul 2009 10:36:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=3239#comment-9665</guid>
		<description>Nice tips.

I completely agree that teams need to limit the amount of &quot;spikes&quot; in an iteration - I&#039;ve seen iterations with no output at all because of &quot;spike abuse&quot;.

Another thing you have to keep an eye on are bug fixing tasks. I&#039;ve seen teams treating them as a separate backlog and that usually leads to either an infinite bug backlog (because of the usual lower priority assigned to them) or developers only working on bug fixes because they seem simpler to do, causing massive delay on the feature backlog.</description>
		<content:encoded><![CDATA[<p>Nice tips.</p>
<p>I completely agree that teams need to limit the amount of &#8220;spikes&#8221; in an iteration &#8211; I&#8217;ve seen iterations with no output at all because of &#8220;spike abuse&#8221;.</p>
<p>Another thing you have to keep an eye on are bug fixing tasks. I&#8217;ve seen teams treating them as a separate backlog and that usually leads to either an infinite bug backlog (because of the usual lower priority assigned to them) or developers only working on bug fixes because they seem simpler to do, causing massive delay on the feature backlog.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark&#8217;s Link Blog &#187; links for 2009-07-16</title>
		<link>http://pathfindersoftware.com/2009/07/what-should-a-good-iteration-contain/#comment-9664</link>
		<dc:creator>Mark&#8217;s Link Blog &#187; links for 2009-07-16</dc:creator>
		<pubDate>Fri, 17 Jul 2009 06:04:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=3239#comment-9664</guid>
		<description>[...] Agile Ajax » What should a good iteration contain » Pathfinder Development (tags: agile iteration story xp scrum) [...]</description>
		<content:encoded><![CDATA[<p>[...] Agile Ajax » What should a good iteration contain » Pathfinder Development (tags: agile iteration story xp scrum) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic (User agent is rejected)
Page Caching using memcached (User agent is rejected)

Served from: pathfindersoftware.com @ 2012-02-10 01:52:09 -->
