<?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 to release a software project</title>
	<atom:link href="http://www.seancolombo.com/2010/01/24/when-to-release-a-software-project/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.seancolombo.com/2010/01/24/when-to-release-a-software-project/</link>
	<description>My little corner of the internet.</description>
	<lastBuildDate>Thu, 29 Jul 2010 17:32:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: bfunk</title>
		<link>http://www.seancolombo.com/2010/01/24/when-to-release-a-software-project/comment-page-1/#comment-29399</link>
		<dc:creator>bfunk</dc:creator>
		<pubDate>Mon, 25 Jan 2010 14:13:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.seancolombo.com/?p=215#comment-29399</guid>
		<description>Every situation is different, of course, but in general, I agree.  Another benefit to releasing as soon as possible is *real* user feedback.  As developers, we can try to guess what our users will want, or even talk to users about what they say they want, but in my experience, you&#039;ll get much better feedback and ideas from a user when he/she actually sees it, and interacts with it.

Incidentally, these people aren&#039;t actually users until they *use* your software!  Until then, they are just *potential* users, and the more you can do to help them see value, the better chance they will become *actual* users.  What better way to see the value that to actually use something!</description>
		<content:encoded><![CDATA[<p>Every situation is different, of course, but in general, I agree.  Another benefit to releasing as soon as possible is *real* user feedback.  As developers, we can try to guess what our users will want, or even talk to users about what they say they want, but in my experience, you&#8217;ll get much better feedback and ideas from a user when he/she actually sees it, and interacts with it.</p>
<p>Incidentally, these people aren&#8217;t actually users until they *use* your software!  Until then, they are just *potential* users, and the more you can do to help them see value, the better chance they will become *actual* users.  What better way to see the value that to actually use something!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
