<?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: When FIT doesn&#8217;t fit</title>
	<atom:link href="http://javidjamae.com/2006/08/11/when-fit-doesnt-fit/feed/" rel="self" type="application/rss+xml" />
	<link>http://javidjamae.com/2006/08/11/when-fit-doesnt-fit/</link>
	<description>Javid Jamae's thoughts on Java, software, and other random things</description>
	<pubDate>Thu, 29 Jul 2010 13:13:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Marcus Ahnve</title>
		<link>http://javidjamae.com/2006/08/11/when-fit-doesnt-fit/comment-page-1/#comment-26</link>
		<dc:creator>Marcus Ahnve</dc:creator>
		<pubDate>Mon, 11 Sep 2006 07:37:00 +0000</pubDate>
		<guid isPermaLink="false">http://javidjamae.com/?p=124#comment-26</guid>
		<description>I completely agree with you that Fit gives no extra value if your stakeholders are not present, or care to follow development. If that is the case though, you probably have worse problems than them not reading test results.&lt;br/&gt;&lt;br/&gt;As far as version control goes, I've settled on HTML on as my format of choice. It was the way Ward designed originally, and I believe it to still be the best way.&lt;br/&gt;&lt;br/&gt;I have come to like the fact that stakeholders can easily see progress right next to the story text is really good. However, the whole thing is still feels clumsy and ugly. I am tinkering with an alternative solution that uses Markdown instead of standard HTML, we'll see where it ends.</description>
		<content:encoded><![CDATA[<p>I completely agree with you that Fit gives no extra value if your stakeholders are not present, or care to follow development. If that is the case though, you probably have worse problems than them not reading test results.</p>
<p>As far as version control goes, I&#8217;ve settled on HTML on as my format of choice. It was the way Ward designed originally, and I believe it to still be the best way.</p>
<p>I have come to like the fact that stakeholders can easily see progress right next to the story text is really good. However, the whole thing is still feels clumsy and ugly. I am tinkering with an alternative solution that uses Markdown instead of standard HTML, we&#8217;ll see where it ends.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
