<?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 for Agilesparks Blog</title>
	<atom:link href="http://agilesparks.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://agilesparks.wordpress.com</link>
	<description>Insights on Agile/Scrum/Lean from the Agilesparks coachers team</description>
	<lastBuildDate>Wed, 10 Jun 2009 18:31:06 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Agile antipattern: Code freezes during each iteration by Iterate / Inspect and Adapt – nice in theory… &#171; Agilesparks Blog</title>
		<link>http://agilesparks.wordpress.com/2009/06/04/agile-antipattern-code-freezes-during-each-iteration/#comment-3</link>
		<dc:creator>Iterate / Inspect and Adapt – nice in theory… &#171; Agilesparks Blog</dc:creator>
		<pubDate>Wed, 10 Jun 2009 18:31:06 +0000</pubDate>
		<guid isPermaLink="false">http://agilesparks.wordpress.com/2009/06/04/agile-antipattern-code-freezes-during-each-iteration/#comment-3</guid>
		<description>[...] Wait – you mean we actually want to have this potentially shippable every iteration? That means we need to have it stable. In order to reach stability we need to do a test cycle. We need some time to do that. The term &#8220;Feature/Code Freeze&#8221; usually comes up at that point. See my earlier post about this. [...]</description>
		<content:encoded><![CDATA[<p>[...] Wait – you mean we actually want to have this potentially shippable every iteration? That means we need to have it stable. In order to reach stability we need to do a test cycle. We need some time to do that. The term &#8220;Feature/Code Freeze&#8221; usually comes up at that point. See my earlier post about this. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Iterate / Inspect and Adapt – nice in theory… by The cost of iterations applied to Kanban as well… &#171; Agilesparks Blog</title>
		<link>http://agilesparks.wordpress.com/2009/06/10/iterate-inspect-and-adapt-%e2%80%93-nice-in-theory%e2%80%a6/#comment-2</link>
		<dc:creator>The cost of iterations applied to Kanban as well… &#171; Agilesparks Blog</dc:creator>
		<pubDate>Wed, 10 Jun 2009 15:10:33 +0000</pubDate>
		<guid isPermaLink="false">http://agilesparks.wordpress.com/?p=36#comment-2</guid>
		<description>[...] 10, 2009 at 6:03 pm &#183; Filed under Uncategorized   My latest blog post was about the costs and challenges of iterations, as well as what to do to overcome [...]</description>
		<content:encoded><![CDATA[<p>[...] 10, 2009 at 6:03 pm &#183; Filed under Uncategorized   My latest blog post was about the costs and challenges of iterations, as well as what to do to overcome [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
