<?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: How Do You Group Projects Into Programs?</title>
	<atom:link href="http://www.pmhut.com/how-do-you-group-projects-into-programs/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/how-do-you-group-projects-into-programs</link>
	<description></description>
	<pubDate>Wed, 23 May 2012 09:20:37 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Pradeep Bhanot</title>
		<link>http://www.pmhut.com/how-do-you-group-projects-into-programs/comment-page-1#comment-3669</link>
		<dc:creator>Pradeep Bhanot</dc:creator>
		<pubDate>Wed, 10 Jun 2009 08:41:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=3280#comment-3669</guid>
		<description>Vaughn I agree with you that top-down is usually the way to go. I have always thought of a program or initiative as a set of projects that roll up to a common set of goals, with common evaluation criteria, which I think of as a kind of portfolio. You provide a teaser to the solution to the disconnect between the projects that commonly happens when you don’t treat them as a portfolio and you stress the need for a common view of all the projects.</description>
		<content:encoded><![CDATA[<p>Vaughn I agree with you that top-down is usually the way to go. I have always thought of a program or initiative as a set of projects that roll up to a common set of goals, with common evaluation criteria, which I think of as a kind of portfolio. You provide a teaser to the solution to the disconnect between the projects that commonly happens when you don’t treat them as a portfolio and you stress the need for a common view of all the projects.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

