<?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: The Big Freaking Requirements Document Must Die. Here&#8217;s Why.</title>
	<atom:link href="http://www.chrisgurney.ca/2010/03/08/big-freaking-requirements-documents/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.chrisgurney.ca/2010/03/08/big-freaking-requirements-documents/</link>
	<description>Chris Gurney on software productization, productivity, and other geekery.</description>
	<lastBuildDate>Wed, 20 Oct 2010 19:07:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chris Gurney</title>
		<link>http://www.chrisgurney.ca/2010/03/08/big-freaking-requirements-documents/comment-page-1/#comment-9097</link>
		<dc:creator>Chris Gurney</dc:creator>
		<pubDate>Wed, 20 Oct 2010 19:07:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrisgurney.ca/?p=253#comment-9097</guid>
		<description>Hi Gareth,

Thanks for the comment!  

The replacement is really a tool that combines all of those aspects into a cohesive package. There are a few vendors in the market of Requirements Definition; in particular, however, you might want to look at Blueprint Requirements Center -- I wrote this post that you just read while I was working there: 

http://www.blueprintsys.com/

Good luck!

Chris.</description>
		<content:encoded><![CDATA[<p>Hi Gareth,</p>
<p>Thanks for the comment!  </p>
<p>The replacement is really a tool that combines all of those aspects into a cohesive package. There are a few vendors in the market of Requirements Definition; in particular, however, you might want to look at Blueprint Requirements Center &#8212; I wrote this post that you just read while I was working there: </p>
<p><a href="http://www.blueprintsys.com/" rel="nofollow">http://www.blueprintsys.com/</a></p>
<p>Good luck!</p>
<p>Chris.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gareth</title>
		<link>http://www.chrisgurney.ca/2010/03/08/big-freaking-requirements-documents/comment-page-1/#comment-9096</link>
		<dc:creator>Gareth</dc:creator>
		<pubDate>Tue, 19 Oct 2010 06:44:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrisgurney.ca/?p=253#comment-9096</guid>
		<description>Great article... but you identify the problem without suggesting a solution. What&#039;s the answer? If we kill our big fat MRD, (or our sparse and equally inadequate one), what do we replace it with?</description>
		<content:encoded><![CDATA[<p>Great article&#8230; but you identify the problem without suggesting a solution. What&#8217;s the answer? If we kill our big fat MRD, (or our sparse and equally inadequate one), what do we replace it with?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: In Defence of the Big Freaking Requirements Document &#124; On Product Management</title>
		<link>http://www.chrisgurney.ca/2010/03/08/big-freaking-requirements-documents/comment-page-1/#comment-9095</link>
		<dc:creator>In Defence of the Big Freaking Requirements Document &#124; On Product Management</dc:creator>
		<pubDate>Fri, 08 Oct 2010 03:59:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrisgurney.ca/?p=253#comment-9095</guid>
		<description>[...] talking about those long requirements documents that people used to write, but that get little if any respect [...]</description>
		<content:encoded><![CDATA[<p>[...] talking about those long requirements documents that people used to write, but that get little if any respect [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

