<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Five guidelines to prioritize feature requests</title>
	<atom:link href="http://productmanagementtips.com/2008/05/05/five-guidelines-to-prioritize-feature-requests/feed/" rel="self" type="application/rss+xml" />
	<link>http://productmanagementtips.com/2008/05/05/five-guidelines-to-prioritize-feature-requests/</link>
	<description>Practical software product management tips</description>
	<lastBuildDate>Wed, 15 Feb 2012 20:10:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Resume formats</title>
		<link>http://productmanagementtips.com/2008/05/05/five-guidelines-to-prioritize-feature-requests/#comment-2101</link>
		<dc:creator><![CDATA[Resume formats]]></dc:creator>
		<pubDate>Thu, 16 Sep 2010 12:23:56 +0000</pubDate>
		<guid isPermaLink="false">http://gopalshenoy.wordpress.com/?p=102#comment-2101</guid>
		<description><![CDATA[Customer service does not mean availability of product, now a days every where products are available to make good relationship with customers help company always]]></description>
		<content:encoded><![CDATA[<p>Customer service does not mean availability of product, now a days every where products are available to make good relationship with customers help company always</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Weekly Reader: 16May08 » The Productologist</title>
		<link>http://productmanagementtips.com/2008/05/05/five-guidelines-to-prioritize-feature-requests/#comment-475</link>
		<dc:creator><![CDATA[Weekly Reader: 16May08 » The Productologist]]></dc:creator>
		<pubDate>Tue, 01 Jul 2008 04:30:25 +0000</pubDate>
		<guid isPermaLink="false">http://gopalshenoy.wordpress.com/?p=102#comment-475</guid>
		<description><![CDATA[[...]  Five guidelines to prioritize feature requests [Product Management Tips] [...]]]></description>
		<content:encoded><![CDATA[<p>[...]  Five guidelines to prioritize feature requests [Product Management Tips] [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://productmanagementtips.com/2008/05/05/five-guidelines-to-prioritize-feature-requests/#comment-449</link>
		<dc:creator><![CDATA[Dave]]></dc:creator>
		<pubDate>Mon, 09 Jun 2008 07:14:38 +0000</pubDate>
		<guid isPermaLink="false">http://gopalshenoy.wordpress.com/?p=102#comment-449</guid>
		<description><![CDATA[Prioritize on revenues. Revenues only show up if the functionality provides value to a customer base large enough to pay for it.]]></description>
		<content:encoded><![CDATA[<p>Prioritize on revenues. Revenues only show up if the functionality provides value to a customer base large enough to pay for it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Weekend Reader: 16May08 » The Productologist</title>
		<link>http://productmanagementtips.com/2008/05/05/five-guidelines-to-prioritize-feature-requests/#comment-419</link>
		<dc:creator><![CDATA[Weekend Reader: 16May08 » The Productologist]]></dc:creator>
		<pubDate>Fri, 16 May 2008 14:28:20 +0000</pubDate>
		<guid isPermaLink="false">http://gopalshenoy.wordpress.com/?p=102#comment-419</guid>
		<description><![CDATA[[...]  Five guidelines to prioritize feature requests [Product Management Tips] [...]]]></description>
		<content:encoded><![CDATA[<p>[...]  Five guidelines to prioritize feature requests [Product Management Tips] [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

