<?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: Dangers of Prototyping</title>
	<atom:link href="http://kosmaczewski.net/2008/08/15/dangers-of-prototypin/feed/" rel="self" type="application/rss+xml" />
	<link>http://kosmaczewski.net/2008/08/15/dangers-of-prototypin/</link>
	<description>sin incertidumbre no hay novedad, sin novedad posible no hay más que repetición y, por lo tanto, negación del otro como un ser libre: el ser libre es un ser incierto. (adrian mancuso)</description>
	<lastBuildDate>Sat, 13 Mar 2010 11:33:20 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Improbable</title>
		<link>http://kosmaczewski.net/2008/08/15/dangers-of-prototypin/comment-page-1/#comment-20674</link>
		<dc:creator>Improbable</dc:creator>
		<pubDate>Wed, 27 Aug 2008 14:07:52 +0000</pubDate>
		<guid isPermaLink="false">http://kosmaczewski.net/?p=1250#comment-20674</guid>
		<description>I&#039;ve used prototypes once. I was the manager so I decided to do it.

Honestly, I can have two visions of what happened, and I don&#039;t know which one is true, both or neither.

The first view of what happened: using prototypes allowed the client to rise the expectations and exigence on the final product. While it was good for the client, we had to work harder and the project profitability suffered

The second view point is that the client was extremelly hard, and using prototypes saved us for a big trouble at the end of the project. We used prototypes just to acomodate change in early steps.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve used prototypes once. I was the manager so I decided to do it.</p>
<p>Honestly, I can have two visions of what happened, and I don&#8217;t know which one is true, both or neither.</p>
<p>The first view of what happened: using prototypes allowed the client to rise the expectations and exigence on the final product. While it was good for the client, we had to work harder and the project profitability suffered</p>
<p>The second view point is that the client was extremelly hard, and using prototypes saved us for a big trouble at the end of the project. We used prototypes just to acomodate change in early steps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian</title>
		<link>http://kosmaczewski.net/2008/08/15/dangers-of-prototypin/comment-page-1/#comment-20124</link>
		<dc:creator>Adrian</dc:creator>
		<pubDate>Sat, 16 Aug 2008 08:30:59 +0000</pubDate>
		<guid isPermaLink="false">http://kosmaczewski.net/?p=1250#comment-20124</guid>
		<description>Hi Peldi! Thanks for your link, excellent work! Indeed your tool seems really interesting. I&#039;m sure to get back to you soon ;)</description>
		<content:encoded><![CDATA[<p>Hi Peldi! Thanks for your link, excellent work! Indeed your tool seems really interesting. I&#8217;m sure to get back to you soon ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peldi Guilizzoni</title>
		<link>http://kosmaczewski.net/2008/08/15/dangers-of-prototypin/comment-page-1/#comment-20123</link>
		<dc:creator>Peldi Guilizzoni</dc:creator>
		<pubDate>Sat, 16 Aug 2008 08:13:02 +0000</pubDate>
		<guid isPermaLink="false">http://kosmaczewski.net/?p=1250#comment-20123</guid>
		<description>Hi there, nice article, thanks! I have also found that without a simple prototype, or at least a mockup of what the UI should do, the end results are not as simple/usable as they could have or should have been. I built a little wireframing tool to sketch out GUI mockups quickly, while maintaining an unpolished pencil and paper look and feel. I&#039;d love to get your feedback on it: http://www.balsamiq.com/products/mockups - let me know if you&#039;d like a full license to evaluate it!</description>
		<content:encoded><![CDATA[<p>Hi there, nice article, thanks! I have also found that without a simple prototype, or at least a mockup of what the UI should do, the end results are not as simple/usable as they could have or should have been. I built a little wireframing tool to sketch out GUI mockups quickly, while maintaining an unpolished pencil and paper look and feel. I&#8217;d love to get your feedback on it: <a href="http://www.balsamiq.com/products/mockups" rel="nofollow">http://www.balsamiq.com/products/mockups</a> &#8211; let me know if you&#8217;d like a full license to evaluate it!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
