<?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: The Practical CIO: Difficulties in project prioritization &amp; selection, part 1</title>
	<atom:link href="http://www.peterkretzman.com/2009/07/31/the-practical-cio-difficulties-in-project-prioritization-selection-part-1/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.peterkretzman.com/2009/07/31/the-practical-cio-difficulties-in-project-prioritization-selection-part-1/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=the-practical-cio-difficulties-in-project-prioritization-selection-part-1</link>
	<description>Intensely practical tips on information technology management, by Peter Kretzman</description>
	<lastBuildDate>Thu, 02 Feb 2012 16:24:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Yang Lu</title>
		<link>http://www.peterkretzman.com/2009/07/31/the-practical-cio-difficulties-in-project-prioritization-selection-part-1/comment-page-1/#comment-9738</link>
		<dc:creator>Yang Lu</dc:creator>
		<pubDate>Tue, 25 Jan 2011 22:31:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterkretzman.com/2009/07/31/the-practical-cio-difficulties-in-project-prioritization-selection-part-1/#comment-9738</guid>
		<description>Hi,

I stumbled onto your blog when I was doing some research on competition.  I really enjoy your blog.

I wanted to make a comment about point 2 -- the &quot;common&quot; thought that many organizations are using C-level execs to do project selection.

There is actually a step prior to selecting the RIGHT projects to do, that is the C-level execs should decide on the direction of the company (ie: a roadmap) and assign a top down budget to that particular strategy.  For instance, company X has $50MM to invest in 2011, the CEO/CIO/CTO must then decide the split of that $50MM -- perhaps we are in a recession, so let&#039;s minimize new and visionary products and focus more on enhancements to the current offering.  Each of those strategies will get a quantifiable top down investment which will:
(1) determine your scorecard criteria for the RIGHT projects to do.
(2) determine whether you should get more internal/external resources and whether you have the finances (top down meets bottom up) so you CAN do the projects.

It is up to the C-level execs to make strategic decisions and let portfolio/pipeline managers (SVP of Technology or the likes) do the actual selection of projects.

Full Disclosure: I currently work at CA Clarity and have worked for Planisware.</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I stumbled onto your blog when I was doing some research on competition.  I really enjoy your blog.</p>
<p>I wanted to make a comment about point 2 &#8212; the &#8220;common&#8221; thought that many organizations are using C-level execs to do project selection.</p>
<p>There is actually a step prior to selecting the RIGHT projects to do, that is the C-level execs should decide on the direction of the company (ie: a roadmap) and assign a top down budget to that particular strategy.  For instance, company X has $50MM to invest in 2011, the CEO/CIO/CTO must then decide the split of that $50MM &#8212; perhaps we are in a recession, so let&#8217;s minimize new and visionary products and focus more on enhancements to the current offering.  Each of those strategies will get a quantifiable top down investment which will:<br />
(1) determine your scorecard criteria for the RIGHT projects to do.<br />
(2) determine whether you should get more internal/external resources and whether you have the finances (top down meets bottom up) so you CAN do the projects.</p>
<p>It is up to the C-level execs to make strategic decisions and let portfolio/pipeline managers (SVP of Technology or the likes) do the actual selection of projects.</p>
<p>Full Disclosure: I currently work at CA Clarity and have worked for Planisware.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IT, the CIO, and the business need for &#8220;roof projects&#8221;</title>
		<link>http://www.peterkretzman.com/2009/07/31/the-practical-cio-difficulties-in-project-prioritization-selection-part-1/comment-page-1/#comment-9425</link>
		<dc:creator>IT, the CIO, and the business need for &#8220;roof projects&#8221;</dc:creator>
		<pubDate>Thu, 16 Sep 2010 01:08:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterkretzman.com/2009/07/31/the-practical-cio-difficulties-in-project-prioritization-selection-part-1/#comment-9425</guid>
		<description>[...] a future post, I&#8217;ll expand further on this topic, talking more about the difficulties of and approaches for [...]</description>
		<content:encoded><![CDATA[<p>[...] a future post, I&#8217;ll expand further on this topic, talking more about the difficulties of and approaches for [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The title issue revisited: CTO vs. CIO</title>
		<link>http://www.peterkretzman.com/2009/07/31/the-practical-cio-difficulties-in-project-prioritization-selection-part-1/comment-page-1/#comment-9317</link>
		<dc:creator>The title issue revisited: CTO vs. CIO</dc:creator>
		<pubDate>Sun, 08 Aug 2010 05:12:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterkretzman.com/2009/07/31/the-practical-cio-difficulties-in-project-prioritization-selection-part-1/#comment-9317</guid>
		<description>[...] posted myself, early and often, on myriad ways to push effectively for IT/business alignment. So I&#8217;m anything but a blind proponent for a [...]</description>
		<content:encoded><![CDATA[<p>[...] posted myself, early and often, on myriad ways to push effectively for IT/business alignment. So I&#8217;m anything but a blind proponent for a [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Whole Portfolio &#171; An IT View</title>
		<link>http://www.peterkretzman.com/2009/07/31/the-practical-cio-difficulties-in-project-prioritization-selection-part-1/comment-page-1/#comment-8731</link>
		<dc:creator>The Whole Portfolio &#171; An IT View</dc:creator>
		<pubDate>Fri, 23 Oct 2009 16:03:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterkretzman.com/2009/07/31/the-practical-cio-difficulties-in-project-prioritization-selection-part-1/#comment-8731</guid>
		<description>[...] comments and the links he provided and I would encourage anyone to go back and look at those posts. Lots of good ideas, challenges, and issues highlighted in his comprehensive post. I wanted to focus on a few key points when I think of balancing the whole portfolio or [...]</description>
		<content:encoded><![CDATA[<p>[...] comments and the links he provided and I would encourage anyone to go back and look at those posts. Lots of good ideas, challenges, and issues highlighted in his comprehensive post. I wanted to focus on a few key points when I think of balancing the whole portfolio or [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Conventional wisdom that fails for IT</title>
		<link>http://www.peterkretzman.com/2009/07/31/the-practical-cio-difficulties-in-project-prioritization-selection-part-1/comment-page-1/#comment-8709</link>
		<dc:creator>Conventional wisdom that fails for IT</dc:creator>
		<pubDate>Fri, 16 Oct 2009 00:46:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterkretzman.com/2009/07/31/the-practical-cio-difficulties-in-project-prioritization-selection-part-1/#comment-8709</guid>
		<description>[...] philosophy of &#8220;consensus&#8221; no matter what. As with a PPM steering committee, you should put effort into designing an effective committee and process, and allow for quick &#8220;tie-breaking&#8221; authority and action as [...]</description>
		<content:encoded><![CDATA[<p>[...] philosophy of &#8220;consensus&#8221; no matter what. As with a PPM steering committee, you should put effort into designing an effective committee and process, and allow for quick &#8220;tie-breaking&#8221; authority and action as [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Practical CIO: Difficulties in project prioritization &#38; selection, part 2</title>
		<link>http://www.peterkretzman.com/2009/07/31/the-practical-cio-difficulties-in-project-prioritization-selection-part-1/comment-page-1/#comment-8601</link>
		<dc:creator>The Practical CIO: Difficulties in project prioritization &#38; selection, part 2</dc:creator>
		<pubDate>Tue, 25 Aug 2009 20:26:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterkretzman.com/2009/07/31/the-practical-cio-difficulties-in-project-prioritization-selection-part-1/#comment-8601</guid>
		<description>[...] Last time, I wrote about ways to pick projects that satisfy the company&#8217;s &#8220;SHOULD do&#8221; dimension: ones that are strategic, financially beneficial, risk mitigating, or legally mandated, for example. I set out practical guidelines for the process of selection in that dimension, to ensure as level a playing field as is possible.  And I left it for this follow-on post to discuss the other dimension, the &#8220;CAN do&#8221; dimension, which needs to calibrate the list of chosen projects to what can actually be accomplished by the available resources. [...]</description>
		<content:encoded><![CDATA[<p>[...] Last time, I wrote about ways to pick projects that satisfy the company&#8217;s &#8220;SHOULD do&#8221; dimension: ones that are strategic, financially beneficial, risk mitigating, or legally mandated, for example. I set out practical guidelines for the process of selection in that dimension, to ensure as level a playing field as is possible.  And I left it for this follow-on post to discuss the other dimension, the &#8220;CAN do&#8221; dimension, which needs to calibrate the list of chosen projects to what can actually be accomplished by the available resources. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitted by ClearSpringBA</title>
		<link>http://www.peterkretzman.com/2009/07/31/the-practical-cio-difficulties-in-project-prioritization-selection-part-1/comment-page-1/#comment-8582</link>
		<dc:creator>Twitted by ClearSpringBA</dc:creator>
		<pubDate>Fri, 14 Aug 2009 14:34:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterkretzman.com/2009/07/31/the-practical-cio-difficulties-in-project-prioritization-selection-part-1/#comment-8582</guid>
		<description>[...] This post was Twitted by ClearSpringBA [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was Twitted by ClearSpringBA [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitted by ericderaspe</title>
		<link>http://www.peterkretzman.com/2009/07/31/the-practical-cio-difficulties-in-project-prioritization-selection-part-1/comment-page-1/#comment-8579</link>
		<dc:creator>Twitted by ericderaspe</dc:creator>
		<pubDate>Sat, 01 Aug 2009 15:27:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterkretzman.com/2009/07/31/the-practical-cio-difficulties-in-project-prioritization-selection-part-1/#comment-8579</guid>
		<description>[...] This post was Twitted by ericderaspe [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was Twitted by ericderaspe [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

