<?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: 02002 Requirements: From Hype-ful to Helpful</title>
	<atom:link href="http://www.productmanagementchallenges.com/software-requirements-product-requirements/02002/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.productmanagementchallenges.com/software-requirements-product-requirements/02002/</link>
	<description>Real-World Tips and Advice for Software Product Managers</description>
	<pubDate>Thu,  9 Sep 2010 07:44:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Jacques Murphy</title>
		<link>http://www.productmanagementchallenges.com/software-requirements-product-requirements/02002/#comment-5</link>
		<dc:creator>Jacques Murphy</dc:creator>
		<pubDate>Wed, 12 Mar 2008 01:56:05 +0000</pubDate>
		<guid isPermaLink="false">http://productmanagementchallenges.com/software-requirements-product-requirements/software-requirements/#comment-5</guid>
		<description>This was the first article I ever wrote about software requirements. The topic of requirements is a central one for product managers, not to mention extensive.

I have found that with all that can be said about how to be successful with software requirements, one of the first, and easiest ways to make a difference is to take out the &lt;em&gt;hype&lt;/em&gt; from the way they are worded, getting everyone focused on the facts.

Another interesting article on requirements is &lt;a href="index.php?p=53&#038;phpMyAdmin=ZEYYZD-INsbwmwhSEZoxryppoMe" rel="nofollow"&gt;03039 ROI and ROR: Return on Requirements&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>This was the first article I ever wrote about software requirements. The topic of requirements is a central one for product managers, not to mention extensive.</p>
<p>I have found that with all that can be said about how to be successful with software requirements, one of the first, and easiest ways to make a difference is to take out the <em>hype</em> from the way they are worded, getting everyone focused on the facts.</p>
<p>Another interesting article on requirements is <a href="index.php?p=53&#038;phpMyAdmin=ZEYYZD-INsbwmwhSEZoxryppoMe" rel="nofollow">03039 ROI and ROR: Return on Requirements</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacques Murphy</title>
		<link>http://www.productmanagementchallenges.com/software-requirements-product-requirements/02002/#comment-4</link>
		<dc:creator>Jacques Murphy</dc:creator>
		<pubDate>Wed, 12 Mar 2008 01:51:10 +0000</pubDate>
		<guid isPermaLink="false">http://productmanagementchallenges.com/software-requirements-product-requirements/software-requirements/#comment-4</guid>
		<description>Click &lt;em&gt;Software Requirements&lt;/em&gt; under &lt;em&gt;Categories&lt;/em&gt; to see articles on similar topics.</description>
		<content:encoded><![CDATA[<p>Click <em>Software Requirements</em> under <em>Categories</em> to see articles on similar topics.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
