<?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: Tactical or Strategic PPM	</title>
	<atom:link href="https://ppmexecution.com/tactical-or-strategic-ppm/feed/" rel="self" type="application/rss+xml" />
	<link>https://ppmexecution.com/tactical-or-strategic-ppm/</link>
	<description>A portfolio management knowledge (PPM) center promoting strategic leadership for strategic execution through project portfolio management</description>
	<lastBuildDate>Sat, 02 Aug 2014 23:47:02 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.2</generator>
	<item>
		<title>
		By: Tim Washington		</title>
		<link>https://ppmexecution.com/tactical-or-strategic-ppm/#comment-2674</link>

		<dc:creator><![CDATA[Tim Washington]]></dc:creator>
		<pubDate>Mon, 31 Dec 2012 06:30:39 +0000</pubDate>
		<guid isPermaLink="false">http://ppmexecution.com/?p=268#comment-2674</guid>

					<description><![CDATA[Hi Sue, thank you for the comments. We are focused on sequencing because the organization has chosen not to prioritize any project work. In lieu of prioritizing,  we are trying to do a better job of sequencing. The dependencies are a pseudo-priority based on the downstream impacts. I may not have expressed myself well, but it turns out that we are doing something similar to what you are talking about--there are many &quot;capabilities&quot; needed to support downstream projects, so we are trying to take a more careful approach to initiating new projects based on these dependencies. The capabilities themselves are not strategic, but they support important projects. I was using the word &#039;tactical&#039; in contrast to &#039;strategic&#039; because we are not considering projects from a strategic point of view and are not &quot;doing&quot; portfolio management from a traditional sense, hence the idea of &quot;tactical portfolio management.&quot; Nevertheless, we are doing some portfolio planning by considering the whole portfolio from a more tactical perspective. Thanks again.]]></description>
			<content:encoded><![CDATA[<p>Hi Sue, thank you for the comments. We are focused on sequencing because the organization has chosen not to prioritize any project work. In lieu of prioritizing,  we are trying to do a better job of sequencing. The dependencies are a pseudo-priority based on the downstream impacts. I may not have expressed myself well, but it turns out that we are doing something similar to what you are talking about&#8211;there are many &#8220;capabilities&#8221; needed to support downstream projects, so we are trying to take a more careful approach to initiating new projects based on these dependencies. The capabilities themselves are not strategic, but they support important projects. I was using the word &#8216;tactical&#8217; in contrast to &#8216;strategic&#8217; because we are not considering projects from a strategic point of view and are not &#8220;doing&#8221; portfolio management from a traditional sense, hence the idea of &#8220;tactical portfolio management.&#8221; Nevertheless, we are doing some portfolio planning by considering the whole portfolio from a more tactical perspective. Thanks again.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Sue Bivins		</title>
		<link>https://ppmexecution.com/tactical-or-strategic-ppm/#comment-2670</link>

		<dc:creator><![CDATA[Sue Bivins]]></dc:creator>
		<pubDate>Sat, 22 Dec 2012 14:52:11 +0000</pubDate>
		<guid isPermaLink="false">http://ppmexecution.com/?p=268#comment-2670</guid>

					<description><![CDATA[Tim, great blogs and I like your concept of tactical portfolio management to manage sequencing and prevent resource conflict. Just a thought -- some dependencies may not be sequence-oriented. Projects with low direct strategic value may be pre-requisite or co-requisite as enablers for projects with high strategic value. These dependencies are thus strategic in nature and should be considered upstream of the project sequencing that is part of tactical portfolio management.]]></description>
			<content:encoded><![CDATA[<p>Tim, great blogs and I like your concept of tactical portfolio management to manage sequencing and prevent resource conflict. Just a thought &#8212; some dependencies may not be sequence-oriented. Projects with low direct strategic value may be pre-requisite or co-requisite as enablers for projects with high strategic value. These dependencies are thus strategic in nature and should be considered upstream of the project sequencing that is part of tactical portfolio management.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
