<?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: At CANUX</title>
	<atom:link href="http://www.bplusd.org/2005/09/24/at-canux/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bplusd.org/2005/09/24/at-canux/</link>
	<description>Business + Design</description>
	<pubDate>Thu, 20 Nov 2008 11:15:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Austin</title>
		<link>http://www.bplusd.org/2005/09/24/at-canux/#comment-88</link>
		<dc:creator>Austin</dc:creator>
		<pubDate>Fri, 11 Mar 2005 06:09:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.bplusd.org/2005/09/24/at-canux/#comment-88</guid>
		<description>When reading that, I couldn't help but think the functional spec comes from quick scenarios and prototypes (their nascent UI).

It definitely doesn't need to be formal, but the spec needs to be something. There's nothing like completing 50% of the production to find out you need an entirely new field in the database and associated processing on *every page in the site*.</description>
		<content:encoded><![CDATA[<p>When reading that, I couldn&#8217;t help but think the functional spec comes from quick scenarios and prototypes (their nascent UI).</p>
<p>It definitely doesn&#8217;t need to be formal, but the spec needs to be something. There&#8217;s nothing like completing 50% of the production to find out you need an entirely new field in the database and associated processing on *every page in the site*.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
