<?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: TDD Adoption Strategies Article</title>
	<atom:link href="http://agilepainrelief.com/notesfromatooluser/2009/01/tdd-adoption-strategies-article.html/feed" rel="self" type="application/rss+xml" />
	<link>http://agilepainrelief.com/notesfromatooluser/2009/01/tdd-adoption-strategies-article.html</link>
	<description>Best practices for your goals</description>
	<lastBuildDate>Tue, 07 Feb 2012 08:29:47 -0500</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: TDD: Links, News and Resources (1) &#171; Angel &#8220;Java&#8221; Lopez on Blog</title>
		<link>http://agilepainrelief.com/notesfromatooluser/2009/01/tdd-adoption-strategies-article.html/comment-page-1#comment-30793</link>
		<dc:creator>TDD: Links, News and Resources (1) &#171; Angel &#8220;Java&#8221; Lopez on Blog</dc:creator>
		<pubDate>Tue, 02 Aug 2011 09:44:04 +0000</pubDate>
		<guid isPermaLink="false">http://agilepainrelief.com/2009/01/tdd-adoption-strategies-article/#comment-30793</guid>
		<description>[...] TDD Adoption Strategies Article &#124; Agile Pain Relief http://agilepainrelief.com/notesfromatooluser/2009/01/tdd-adoption-strategies-article.html [...]</description>
		<content:encoded><![CDATA[<p>[...] TDD Adoption Strategies Article | Agile Pain Relief <a href="http://agilepainrelief.com/notesfromatooluser/2009/01/tdd-adoption-strategies-article.html" rel="nofollow">http://agilepainrelief.com/notesfromatooluser/2009/01/tdd-adoption-strategies-article.html</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carlton</title>
		<link>http://agilepainrelief.com/notesfromatooluser/2009/01/tdd-adoption-strategies-article.html/comment-page-1#comment-96</link>
		<dc:creator>Carlton</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://agilepainrelief.com/2009/01/tdd-adoption-strategies-article/#comment-96</guid>
		<description>Your experience matches mine.  &lt;a href=&quot;http://carltonnettleton.com/blog/?p=345&quot; rel=&quot;nofollow&quot;&gt;Read more at Crouch, Touch, Pause...Engage&lt;/a&gt;


</description>
		<content:encoded><![CDATA[<p>Your experience matches mine.  <a href="http://carltonnettleton.com/blog/?p=345" rel="nofollow">Read more at Crouch, Touch, Pause&#8230;Engage</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Levison</title>
		<link>http://agilepainrelief.com/notesfromatooluser/2009/01/tdd-adoption-strategies-article.html/comment-page-1#comment-97</link>
		<dc:creator>Mark Levison</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://agilepainrelief.com/2009/01/tdd-adoption-strategies-article/#comment-97</guid>
		<description>I&#039;ve just read your blog posting that is another interesting strategy my only question would be around how well does this scale. Can you handle 50 people this way? 200?
</description>
		<content:encoded><![CDATA[<p>I&#8217;ve just read your blog posting that is another interesting strategy my only question would be around how well does this scale. Can you handle 50 people this way? 200?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carlton</title>
		<link>http://agilepainrelief.com/notesfromatooluser/2009/01/tdd-adoption-strategies-article.html/comment-page-1#comment-98</link>
		<dc:creator>Carlton</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://agilepainrelief.com/2009/01/tdd-adoption-strategies-article/#comment-98</guid>
		<description>It works in waves - you work with one group\department at a time.

I have tried the one-day &quot;This is TDD&quot; approach and I would periodically get requests to come back.  For the longest time I could not understand what was wrong and then I realized my approach was wrong.  I was treating the situation like I was an external consultant, but forgot I was an internal consultant and had more flexibility on the schedule of the employees.
</description>
		<content:encoded><![CDATA[<p>It works in waves &#8211; you work with one group\department at a time.</p>
<p>I have tried the one-day &#8220;This is TDD&#8221; approach and I would periodically get requests to come back.  For the longest time I could not understand what was wrong and then I realized my approach was wrong.  I was treating the situation like I was an external consultant, but forgot I was an internal consultant and had more flexibility on the schedule of the employees.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

