<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Lessons from 100 PMOs &#187; Portfolio Management</title>
	<atom:link href="http://blog.effectiveitgroup.com/tag/portfolio-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.effectiveitgroup.com</link>
	<description>Real world lessons learned from working with 100+ PMOs</description>
	<lastBuildDate>Tue, 17 Nov 2009 05:01:18 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.3</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>SIR: A new twist on classifying project portfolios</title>
		<link>http://blog.effectiveitgroup.com/2009/11/sir-a-new-twist-on-classifying-project-portfolios/</link>
		<comments>http://blog.effectiveitgroup.com/2009/11/sir-a-new-twist-on-classifying-project-portfolios/#comments</comments>
		<pubDate>Tue, 17 Nov 2009 05:01:18 +0000</pubDate>
		<dc:creator>Dave B</dc:creator>
				<category><![CDATA[Portfolio Management]]></category>
		<category><![CDATA[PMO]]></category>
		<category><![CDATA[Project Management Office]]></category>

		<guid isPermaLink="false">http://blog.effectiveitgroup.com/?p=109</guid>
		<description><![CDATA[I was conducting a portfolio management workshop at one of my favorite clients , VWR,  a couple of weeks ago when the topic of classifying portfolios came up. The usual investment class options came up, namely the MIT model and the Run Grow Transform model.
The MIT model (Strategic, Informational, Transactional, and Infrastructure) was first developed [...]]]></description>
			<content:encoded><![CDATA[<div><span style="font-size: x-small;"><span lang="EN">I was conducting a portfolio management workshop at one of my favorite clients , VWR,  a couple of weeks ago when the topic of classifying portfolios came up. The usual investment class options came up, namely the MIT model and the Run Grow Transform model.</span></span></div>
<div><span style="font-size: x-small;"><span lang="EN">The MIT model (Strategic, Informational, Transactional, and Infrastructure) was first developed by Peter Weill at MIT and made popular by CIO Magazine earlier this decade. I&#8217;ve always felt it provided a nice breakout for IT departments in particular. I actually like seperating Informational projects (decision support) from Transactional (automating business processes). I&#8217;ve never really like the Infrastructure classification, however. While this represents keep the lights on type activities, it can easily be confused with the common perception in IT of the hardware and network infrastructure. In any event, VWR (and many of my clients) felt the model was overly complex and not very intuitive. </span></span></div>
<p><span style="font-size: x-small;"><span lang="EN">So we turned to Run, Grow, Transform. This seemed a much more intuitive scheme. Having just been to a Gartner conference, they of course had  gotten a thorough understanding (this being Gartner&#8217;s preferred model). But there were a couple of issues.</p>
<p>First, they felt that the Transform category had too high a threshold. It is the rare project that actually transforms how a typical company does business (with the exception of the high-tech world, of course). It is much more common for them to undertake strategic projects, which we loosely defined as furthering the strategic goals of the company. I&#8217;ve noticed many PMOs actually use the Transform bucket in this manner. But rather than keep with tradition and simply us Transform to mean strategic, we decided to rename the category.</p>
<p>Next came Grow, which on its face sounds pretty obvious. But does this apply only to projects that help the company grow? What about automation? We supposed that improving efficiency would grow the bottom line, but suddenly this was less intuitive. After bandying about several alternatives it was either Mike or Roger (that&#8217;s Mike Rinehart and Roger Larson to give credit where its due) came up with Improve. This was defined as anything that improves the operations or effectiveness of the organization. This then encompassed the grow projects along with any others that are more than simply maintenance.</p>
<p>Run did seem pretty intuitive. The idea of work required to keep things running (or KLO &#8211; keep the lights on) is pretty self-explanatory, so we kept that.</p>
<p>We then reviewed their portfolio and found we could much more readily identify projects as being in Strategic, Improve, or Run. And what do you know, Mike pointed out it also has an easy acronym &#8211; SIR!</p>
<p>So there you have it, a new project portfolio classification scheme, SIR. What does the community think? I&#8217;m really anxious to hear thoughts on this one!</p>
<p>Dave B.</p>
<p> </p>
<p> </p>
<p></span></span></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.effectiveitgroup.com/2009/11/sir-a-new-twist-on-classifying-project-portfolios/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>A Portfolio of Business Outcomes</title>
		<link>http://blog.effectiveitgroup.com/2009/07/a-portfolio-of-business-outcomes/</link>
		<comments>http://blog.effectiveitgroup.com/2009/07/a-portfolio-of-business-outcomes/#comments</comments>
		<pubDate>Tue, 28 Jul 2009 23:34:19 +0000</pubDate>
		<dc:creator>Dave B</dc:creator>
				<category><![CDATA[Portfolio Management]]></category>
		<category><![CDATA[PMO]]></category>

		<guid isPermaLink="false">http://blog.effectiveitgroup.com/?p=60</guid>
		<description><![CDATA[While project portfolio management owes its genesis to financial portfolio management, there are some key differences. The first is the outcome of the portfolio. With a portfolio of financial assets, such as stocks, the return is measured in the same common denominator: dollars. This allows us to create some common key measures of performance, such as return on assets, price/earnings ratios, ROI, etc.

Projects, however, are not all directly tied to dollars. Some projects improve employee moral, some increase market share, and some simply make current operations more efficient. Another way to look at this is to think of each project as a business outcome. Companies invest in a project to achieve a certain goal. Recent examples from EIG clients include:]]></description>
			<content:encoded><![CDATA[<p>While project portfolio management owes its genesis to financial portfolio management, there are some key differences. The first is the outcome of the portfolio. With a portfolio of financial assets, such as stocks, the return is measured in the same common denominator: dollars. This allows us to create some common key measures of performance, such as return on assets, price/earnings ratios, ROI, etc.</p>
<p>Projects, however, are not all directly tied to dollars. Some projects improve employee moral, some increase market share, and some simply make current operations more efficient. Another way to look at this is to think of each project as a business outcome. Companies invest in a project to achieve a certain goal. Recent examples from EIG clients include:</p>
<p><span id="more-60"></span></p>
<ul>
<li>Web site re-vamp to increase sales and customer satisfaction by streamlining the web experience.</li>
<li>Employee self-service application to improve employee moral and gain efficiencies in HR</li>
<li>SAP implementation to automate financial processes and improve decision support.</li>
<li>Stabilization effort to improve performance of various core apps. For this customer, this should produce increased sales, improved employee satisfaction, and reduced help desk costs.</li>
</ul>
<p>How, then, to look at portfolios of such diverse business outcomes? Rather than simply grouping projects by size or business unit (which is valuable, of course), some companies are now grouping by strategy or like outcomes.</p>
<p>A classic is by investment type, and the two popular models are:</p>
<ul>
<li>Run, Grow, Transform</li>
<li>Strategic, Informational, Transactional, Infrastructure</li>
</ul>
<p>Portfolios of like outcomes might look like:</p>
<ul>
<li>Employee projects</li>
<li>Customer projects</li>
<li>Transaction automation projects</li>
<li>Infrastructure projects</li>
</ul>
<p>Portfolios by strategy might look like:</p>
<ul>
<li>Gain market leadership</li>
<li>Most satisfied employees</li>
<li>Double revenues</li>
<li>Low cost provider</li>
</ul>
<p>Wait a minute, does this look like strategic alignment? You bet it does! But then, that&#8217;s the real reason we start projects in the first place &#8211; to better execute company strategy. And that&#8217;s why all projects should be aimed at business outcomes, not simple financial metrics.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.effectiveitgroup.com/2009/07/a-portfolio-of-business-outcomes/feed/</wfw:commentRss>
		<slash:comments>162</slash:comments>
		</item>
		<item>
		<title>Project Intake: The sales funnel for PMOs</title>
		<link>http://blog.effectiveitgroup.com/2009/05/project-intake-the-sales-funnel-for-pmos/</link>
		<comments>http://blog.effectiveitgroup.com/2009/05/project-intake-the-sales-funnel-for-pmos/#comments</comments>
		<pubDate>Fri, 15 May 2009 23:20:31 +0000</pubDate>
		<dc:creator>Dave B</dc:creator>
				<category><![CDATA[Prioritization and Selection]]></category>
		<category><![CDATA[Initiation]]></category>
		<category><![CDATA[PMO]]></category>
		<category><![CDATA[Portfolio Management]]></category>

		<guid isPermaLink="false">http://blog.effectiveitgroup.com/?p=51</guid>
		<description><![CDATA[Most PMOs I work with face the same problem: too many project requests and not enough time to do them all! I will admit, I've worked with one group that did not have this problem. They have plenty of money and were told that if it's a worthwhile project, there's ample funding and they can hire all the people they need. If you're in that situation, no need to read on. Rest assured - the rest of us are envious!

But, if you're like the other 99% of PMOs in the world, you need a way to manage this onslaught of potential work.

In the sales world, they have what's known as the sales pipeline or sales funnel. This is a process whereby potential opportunities are matured, step by step, to fruition as a completed sale. Along the way, opportunities fall by the wayside. They may not have budget to buy, may not need the products on offer, or just don't have enough interest.

Sales will draw this process as a funnel that has several stages. At each stage, a number of opportunities will fall out of the pipeline. Hence, the funneling effect. They start as opportunities (hey - I've got someone's phone number!), progress to prospects (they actually my call!), become qualified prospects (they have budget!), and finally customers (wow - they actually signed the contract!)]]></description>
			<content:encoded><![CDATA[<p>Most PMOs I work with face the same problem: too many project requests and not enough time to do them all! I will admit, I&#8217;ve worked with one group that did not have this problem. They have plenty of money and were told that if it&#8217;s a worthwhile project, there&#8217;s ample funding and they can hire all the people they need. If you&#8217;re in that situation, no need to read on. Rest assured &#8211; the rest of us are envious!</p>
<p>But, if you&#8217;re like the other 99% of PMOs in the world, you need a way to manage this onslaught of potential work.</p>
<p>In the sales world, they have what&#8217;s known as the sales pipeline or sales funnel. This is a process whereby potential opportunities are matured, step by step, to fruition as a completed sale. Along the way, opportunities fall by the wayside. They may not have budget to buy, may not need the products on offer, or just don&#8217;t have enough interest.</p>
<p>Sales will draw this process as a funnel that has several stages. At each stage, a number of opportunities will fall out of the pipeline. Hence, the funneling effect. They start as opportunities (hey &#8211; I&#8217;ve got someone&#8217;s phone number!), progress to prospects (they actually my call!), become qualified prospects (they have budget!), and finally customers (wow &#8211; they actually signed the contract!)</p>
<p>What if PMOs could have a similar process? What if we had a funnel that allowed us to qualify project ideas step-by-step?</p>
<p><span id="more-51"></span></p>
<p>Currently, most PMOs take an idea and spend a lot of time and money giving it a full analysis before presenting it for final approval. How much time and money could be saved by funneling those ideas through some filters so that only qualified ideas are analyzed?</p>
<p>That&#8217;s the idea behind a Project Intake process. We start with an idea (hey &#8211; let&#8217;s redo the company website!), progress it to a request (here&#8217;s why we should re-do the website. It&#8217;ll pump up revenues!), qualify the request (the scorecard for the website redesign looks good!), create a full-blown business case (wow &#8211; the numbers for this redesign really pan out), then finally it becomes a project (the committee approved the re-design! Hooray!).</p>
<p>To work effectively, this really should be a portfolio process &#8211; not a project management process. Why? Because as we&#8217;re taking requests through the pipeline, they need to be compared to each other and winnowed down to the organizations ability to execute (budget, resources, and skills). By comparing requests as a slate early on, we can narrow down the number of requests that get the full analysis treatment, saving tons of money. By using a funnel approach, we can ensure the outcome is a portfolio of the most worthwhile projects that fit our organization.</p>
<p>So, do you have an effective Project Intake Funnel? If not, contact us. We can help you design one that fits your organization. And we&#8217;ll do so on an advisory basis, which gets the job done for a lot less than a consultant that looks like an FTE taking up desk space!</p>
<p>Just need a scorecard to help with that initial winnowing? We&#8217;ve got a best-practice scorecard that can be used as a starting point! And, of course, we can help you develop one tailor-made for your PMO.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.effectiveitgroup.com/2009/05/project-intake-the-sales-funnel-for-pmos/feed/</wfw:commentRss>
		<slash:comments>44</slash:comments>
		</item>
	</channel>
</rss>

