<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Code for Concinnity &#187; requirements gathering</title>
	<atom:link href="http://cfc.kizzx2.com/index.php/tag/requirements-gathering/feed/" rel="self" type="application/rss+xml" />
	<link>http://cfc.kizzx2.com</link>
	<description>beautiful and elegant solutions</description>
	<lastBuildDate>Fri, 10 Feb 2012 13:24:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Don&#8217;t gather business requirements: hire domain experts</title>
		<link>http://cfc.kizzx2.com/index.php/dont-gather-business-requirements-hire-domain-experts/</link>
		<comments>http://cfc.kizzx2.com/index.php/dont-gather-business-requirements-hire-domain-experts/#comments</comments>
		<pubDate>Fri, 11 Sep 2009 14:36:39 +0000</pubDate>
		<dc:creator>kizzx2</dc:creator>
				<category><![CDATA[Process]]></category>
		<category><![CDATA[requirements gathering]]></category>
		<category><![CDATA[software requirements]]></category>
		<category><![CDATA[specifications]]></category>

		<guid isPermaLink="false">http://cfc.kizzx2.com/?p=58</guid>
		<description><![CDATA[Recently I&#8217;ve been spending a lot of time researching the topic of software requirements and specifications. The question that I have kept asking myself is &#8220;How I can build something the customer wants from the first place?&#8221; A lot (if not all) of the time, the customer can&#8217;t even describe the correct specifications and requirements [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="margin-left: 10px; float: right;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fcfc.kizzx2.com%2Findex.php%2Fdont-gather-business-requirements-hire-domain-experts%2F">
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fcfc.kizzx2.com%2Findex.php%2Fdont-gather-business-requirements-hire-domain-experts%2F&amp;source=kizzx2&amp;style=normal&amp;b=2" height="61" width="50" />
			</a>
		</div><p>Recently I&#8217;ve been spending a lot of time researching the topic of software requirements and specifications. The question that I have kept asking myself is &#8220;How I can build something the customer wants from the first place?&#8221; A lot (if not all) of the time, the customer can&#8217;t even describe the correct specifications and requirements because he won&#8217;t know it until he sees it.</p>

<p>Then today I read Steve Yegge&#8217;s blog post <a href="http://steve-yegge.blogspot.com/2008/08/business-requirements-are-bullshit.html">&#8220;Business Requirements are Bullshit&#8221;</a> which gave me a pretty profound answer to my question:</p>

<blockquote>
  <p>Don&#8217;t gather business requirements: hire domain experts.</p>
</blockquote>
]]></content:encoded>
			<wfw:commentRss>http://cfc.kizzx2.com/index.php/dont-gather-business-requirements-hire-domain-experts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

