<?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"
	>
<channel>
	<title>Comments on: Interface driven design and testing</title>
	<atom:link href="http://www.fuzzylizard.com/archives/2007/10/17/907/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fuzzylizard.com/archives/2007/10/17/907/</link>
	<description>My thoughts on Agile, Java and Ruby on Rails (mostly)</description>
	<pubDate>Fri, 21 Nov 2008 06:23:18 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Joe Gutierrez</title>
		<link>http://www.fuzzylizard.com/archives/2007/10/17/907/#comment-18753</link>
		<dc:creator>Joe Gutierrez</dc:creator>
		<pubDate>Tue, 23 Oct 2007 14:27:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.fuzzylizard.com/archives/2007/10/17/907/#comment-18753</guid>
		<description>After mocking objects in my unit tests with Ruby, I've found that it is imperative that integration/acceptance tests be created. Especially if using events to drive the application.</description>
		<content:encoded><![CDATA[<p>After mocking objects in my unit tests with Ruby, I&#8217;ve found that it is imperative that integration/acceptance tests be created. Especially if using events to drive the application.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arnon Rotem-Gal-Oz</title>
		<link>http://www.fuzzylizard.com/archives/2007/10/17/907/#comment-18393</link>
		<dc:creator>Arnon Rotem-Gal-Oz</dc:creator>
		<pubDate>Wed, 17 Oct 2007 22:22:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.fuzzylizard.com/archives/2007/10/17/907/#comment-18393</guid>
		<description>While a lot of agilists look at a UI prototype as a forbidden "design up front". I think it is an invaluable tool to help lower risk and provide immediate feedback for an important part of the project. 
The prototype doesn't have to include all the functionality - but it has to deliver the spirit of using the system. The prototype can also evolve screen by screen (and sometimes feature by feature) as the project progresses and in my experience this always customers and end-users love the interaction and their ability to help shape the direction the application they use later</description>
		<content:encoded><![CDATA[<p>While a lot of agilists look at a UI prototype as a forbidden &#8220;design up front&#8221;. I think it is an invaluable tool to help lower risk and provide immediate feedback for an important part of the project.<br />
The prototype doesn&#8217;t have to include all the functionality - but it has to deliver the spirit of using the system. The prototype can also evolve screen by screen (and sometimes feature by feature) as the project progresses and in my experience this always customers and end-users love the interaction and their ability to help shape the direction the application they use later</p>
]]></content:encoded>
	</item>
</channel>
</rss>
