<?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: Why Few Companies Have A Project Management Office (PMO)</title>
	<atom:link href="http://www.pmhut.com/why-few-companies-have-a-project-management-office-pmo/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/why-few-companies-have-a-project-management-office-pmo</link>
	<description></description>
	<pubDate>Fri, 25 May 2012 03:53:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jorge Dominguez, PMP</title>
		<link>http://www.pmhut.com/why-few-companies-have-a-project-management-office-pmo/comment-page-1#comment-9575</link>
		<dc:creator>Jorge Dominguez, PMP</dc:creator>
		<pubDate>Fri, 02 Oct 2009 14:38:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=3435#comment-9575</guid>
		<description>Colleagues,

Thank you all for your comments and I appreciate your reading.

Best regards,
Jorge Dominguez, PMP
www.Expiriance.com</description>
		<content:encoded><![CDATA[<p>Colleagues,</p>
<p>Thank you all for your comments and I appreciate your reading.</p>
<p>Best regards,<br />
Jorge Dominguez, PMP<br />
<a href="http://www.Expiriance.com" rel="nofollow">http://www.Expiriance.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PM Hut</title>
		<link>http://www.pmhut.com/why-few-companies-have-a-project-management-office-pmo/comment-page-1#comment-5731</link>
		<dc:creator>PM Hut</dc:creator>
		<pubDate>Thu, 02 Jul 2009 02:02:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=3435#comment-5731</guid>
		<description>Billene,

There's definitely an overhead associated with a PMO, it doesn't make sense to run a PMO in a very small company, but it is definitely worth it as companies grow bigger.</description>
		<content:encoded><![CDATA[<p>Billene,</p>
<p>There&#8217;s definitely an overhead associated with a PMO, it doesn&#8217;t make sense to run a PMO in a very small company, but it is definitely worth it as companies grow bigger.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Billene Lee</title>
		<link>http://www.pmhut.com/why-few-companies-have-a-project-management-office-pmo/comment-page-1#comment-5730</link>
		<dc:creator>Billene Lee</dc:creator>
		<pubDate>Thu, 02 Jul 2009 01:28:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=3435#comment-5730</guid>
		<description>Operating a PMO office is a cost itself. How do we justify the running cost in the long-run and in the organization's benefit?</description>
		<content:encoded><![CDATA[<p>Operating a PMO office is a cost itself. How do we justify the running cost in the long-run and in the organization&#8217;s benefit?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike McClure</title>
		<link>http://www.pmhut.com/why-few-companies-have-a-project-management-office-pmo/comment-page-1#comment-5721</link>
		<dc:creator>Mike McClure</dc:creator>
		<pubDate>Wed, 01 Jul 2009 22:29:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=3435#comment-5721</guid>
		<description>In my experience, most people who resist the concept of a PMO have had exposure to the "bureaucratic" kind whose focus was mostly process &amp; model compliance. 

Often this has been interpreted as interfering with the job at hand (project deliverables) to fill in forms and templates that had very little alignment with the specific project.

The PMOs I have seen thrive the most are outcome focussed rather than process focussed. These PMOs tend to point "out" to the business owners and position themselves to be all about successful outcomes for the owners. 

This shift in perspective allows the PMO to sell the importance of ensuring good (appropriate) process up the chain, and gives them the mandate to customise process per project (nobody needs to fill in hundreds of pages of templates for a 1 week project). This in turn allows the Project Teams to get on with the business of delivering value.</description>
		<content:encoded><![CDATA[<p>In my experience, most people who resist the concept of a PMO have had exposure to the &#8220;bureaucratic&#8221; kind whose focus was mostly process &amp; model compliance. </p>
<p>Often this has been interpreted as interfering with the job at hand (project deliverables) to fill in forms and templates that had very little alignment with the specific project.</p>
<p>The PMOs I have seen thrive the most are outcome focussed rather than process focussed. These PMOs tend to point &#8220;out&#8221; to the business owners and position themselves to be all about successful outcomes for the owners. </p>
<p>This shift in perspective allows the PMO to sell the importance of ensuring good (appropriate) process up the chain, and gives them the mandate to customise process per project (nobody needs to fill in hundreds of pages of templates for a 1 week project). This in turn allows the Project Teams to get on with the business of delivering value.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

