<?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: Writing Complete Requirements</title>
	<atom:link href="http://tynerblain.com/blog/2006/06/08/writing-complete-requirements/feed/" rel="self" type="application/rss+xml" />
	<link>http://tynerblain.com/blog/2006/06/08/writing-complete-requirements/</link>
	<description>Software product success.</description>
	<lastBuildDate>Thu, 18 Mar 2010 20:39:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ten Requirements Gathering Techniques &#171; Little K&#8217;s Blog</title>
		<link>http://tynerblain.com/blog/2006/06/08/writing-complete-requirements/comment-page-1/#comment-57198</link>
		<dc:creator>Ten Requirements Gathering Techniques &#171; Little K&#8217;s Blog</dc:creator>
		<pubDate>Thu, 23 Nov 2006 05:13:37 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/06/08/writing-complete-requirements/#comment-57198</guid>
		<description>[...] Reviewing the documentation of an existing system can help when creating AS-IS process documents, as well as driving gap analysis for scoping of migration projects. In an ideal world, we would even be reviewing the requirements that drove creation of the existing system - a starting point for documenting current requirements. Nuggets of information are often buried in existing documents that help us ask questions as part of validating requirement completeness. [...]</description>
		<content:encoded><![CDATA[<p>[...] Reviewing the documentation of an existing system can help when creating AS-IS process documents, as well as driving gap analysis for scoping of migration projects. In an ideal world, we would even be reviewing the requirements that drove creation of the existing system &#8211; a starting point for documenting current requirements. Nuggets of information are often buried in existing documents that help us ask questions as part of validating requirement completeness. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
