<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Priorities - part 1</title><link>http://blogs.msdn.com/alanpa/archive/2007/09/19/priorities-part-1.aspx</link><description>On any software project with a hint of a schedule, there are priorities. There are priorities in choosing features, in assigning attributes to bugs, and in overall project management. Priorities guide the product strategy and the day to day work. We have</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Priorities - part 1</title><link>http://blogs.msdn.com/alanpa/archive/2007/09/19/priorities-part-1.aspx#5019818</link><pubDate>Fri, 21 Sep 2007 01:10:13 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5019818</guid><dc:creator>alanpa</dc:creator><description>&lt;p&gt;An alternative to bug queues may be tag clouds for bugs. Some information is here:&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://vaultblog.sourcegear.com/articles/2007/08/30/tag-clouds"&gt;http://vaultblog.sourcegear.com/articles/2007/08/30/tag-clouds&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Thanks Igor for sending this info to me.&lt;/p&gt;
</description></item><item><title>re: Priorities - part 1</title><link>http://blogs.msdn.com/alanpa/archive/2007/09/19/priorities-part-1.aspx#5027890</link><pubDate>Fri, 21 Sep 2007 11:32:56 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5027890</guid><dc:creator>anutthara</dc:creator><description>&lt;p&gt;IMHO, prioritizing bugs is the easier part. Prioritizing features is where the problem comes in. Looking forward to your next post&lt;/p&gt;</description></item></channel></rss>