<?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: What&#8217;s Required of Requirement Management?</title>
	<atom:link href="http://svprojectmanagement.com/whats-required-of-requirement-management/feed" rel="self" type="application/rss+xml" />
	<link>http://svprojectmanagement.com/whats-required-of-requirement-management</link>
	<description>Project management wisdom from practictioners and the UCSC Extension in Silicon Valley</description>
	<lastBuildDate>Tue, 21 May 2013 05:46:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Loyal Mealer</title>
		<link>http://svprojectmanagement.com/whats-required-of-requirement-management#comment-4985</link>
		<dc:creator>Loyal Mealer</dc:creator>
		<pubDate>Fri, 29 May 2009 00:45:10 +0000</pubDate>
		<guid isPermaLink="false">http://svprojectmanagement.com/?p=2386#comment-4985</guid>
		<description><![CDATA[Wonderful summary and recommendations. Unfortunately, organizations that do this well are few and far between. I wonder, is having complete requirements at the outset of a product development effort ALWAYS necessary? What about the tiny startup that pushes out an initial product with little or no requirements actually written down, and then iterates their offering(s) to better server customers as time goes on? In a sense, the requirements are written into the product as it evolves. I suppose you could argue that you need at least SOME decent requirements even for the initial product, or you would not know when you are done enough to release the first version.]]></description>
		<content:encoded><![CDATA[<p>Wonderful summary and recommendations. Unfortunately, organizations that do this well are few and far between. I wonder, is having complete requirements at the outset of a product development effort ALWAYS necessary? What about the tiny startup that pushes out an initial product with little or no requirements actually written down, and then iterates their offering(s) to better server customers as time goes on? In a sense, the requirements are written into the product as it evolves. I suppose you could argue that you need at least SOME decent requirements even for the initial product, or you would not know when you are done enough to release the first version.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

 Served from: svprojectmanagement.com @ 2013-05-25 18:37:41 by W3 Total Cache -->