<?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: Agile Refactoring</title>
	<atom:link href="http://blog.foomonger.com/2009/11/10/agile-refactoring/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.foomonger.com/2009/11/10/agile-refactoring/</link>
	<description>Tips and Musings on Software Development, Flash, and Flex</description>
	<lastBuildDate>Fri, 03 Sep 2010 23:12:38 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Craig Daniel</title>
		<link>http://blog.foomonger.com/2009/11/10/agile-refactoring/comment-page-1/#comment-33</link>
		<dc:creator>Craig Daniel</dc:creator>
		<pubDate>Wed, 18 Nov 2009 18:10:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.foomonger.com/?p=33#comment-33</guid>
		<description>Great post Sam.  A discipline commonly used by XP teams is to keep a backlog of &quot;clean up&quot; tasks.  Then, you can either schedule 10%-20% of the velocity for each iteration for cleanup tasks or you can fix cleanup tasks every 3rd or 4th iteration.

Another key discipline is implementing unit tests, preferably via TDD, that help teams to confidently refactor as they go.

A good product owner knows that he has to pay off his debt at some point or the velocity will suffer.  I spoke to this in more detail on my blog: http://cdan.posterous.com/technical-debt-when-agile-software-developmen</description>
		<content:encoded><![CDATA[<p>Great post Sam.  A discipline commonly used by XP teams is to keep a backlog of &#8220;clean up&#8221; tasks.  Then, you can either schedule 10%-20% of the velocity for each iteration for cleanup tasks or you can fix cleanup tasks every 3rd or 4th iteration.</p>
<p>Another key discipline is implementing unit tests, preferably via TDD, that help teams to confidently refactor as they go.</p>
<p>A good product owner knows that he has to pay off his debt at some point or the velocity will suffer.  I spoke to this in more detail on my blog: <a href="http://cdan.posterous.com/technical-debt-when-agile-software-developmen" rel="nofollow">http://cdan.posterous.com/technical-debt-when-agile-software-developmen</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason</title>
		<link>http://blog.foomonger.com/2009/11/10/agile-refactoring/comment-page-1/#comment-32</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Fri, 13 Nov 2009 17:32:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.foomonger.com/?p=33#comment-32</guid>
		<description>I like adding a #technicaldebt tag to the code.  Kinda like a TODO, but more meaningful.

I tend to refactor as a go along, and build the cost into my user stories.</description>
		<content:encoded><![CDATA[<p>I like adding a #technicaldebt tag to the code.  Kinda like a TODO, but more meaningful.</p>
<p>I tend to refactor as a go along, and build the cost into my user stories.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
