<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Meet Claude Emond</title>
	<link>http://www.reformingprojectmanagement.com/2003/04/12/151/</link>
	<description>The magazine for the project age</description>
	<pubDate>Sun, 12 Oct 2008 19:42:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Claude Emond
        </title>
		<link>http://www.reformingprojectmanagement.com/2003/04/12/151/#comment-331</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2003/04/12/151/#comment-331</guid>
					<description>
        Thanks very much for the topo, Hal. Quite faithful to our exchanges to this day.

Two small comments to keep the record straight:

a) I am a chemical engineer, not a mechanical engineer (must be my funny accent when I speak English). Not a big issue anyway wrt my project management vision.

b) For the PMOs, the 'fad' comment needs a little clarification. The fad is in putting an official box in the organizational structure BEFORE understanding what has to be done to deploy better project management in an organization. Many organizations put into place  physical PMOs (desks with people)with no clear mandate and now official authority on anything. It is a top-down approach that just does not work, because deploying project management implies important cultural-organizational changes with many new roles and responsibilities. Even with formal authority, the work of these PMOs is often viewed as interference to business-as-usual (there has not been any cultural change coming simultaneously), is opposed and sabotaged, any of their directives are just not listened to and bypassed. After a few months, upper management just questions the use of this NEW BOX than does not seem to get along with anybody and has no measurable results for its justification. THEY then just close the PMO (the box) and project management as a core business process will have to wait the next crisis and the coming of a new upper management team. What is important, while evolving towards a project management culture, is to put in place facilitating tools, training, internal consulting, to SUPPORT people in their projects and help them to see by themselves the advantage of applying project management principles and putting in place true project teams working together. And if the organization has the resources, why not provide a 'clearing house' for this facilitating work in the form of a PSO supporting project management rather than that of a PMO taking over (only in its mind) the management of projects.
      </description>
		<content:encoded><![CDATA[<p>Thanks very much for the topo, Hal. Quite faithful to our exchanges to this day.</p>
<p>Two small comments to keep the record straight:</p>
<p>a) I am a chemical engineer, not a mechanical engineer (must be my funny accent when I speak English). Not a big issue anyway wrt my project management vision.</p>
<p>b) For the PMOs, the &#8216;fad&#8217; comment needs a little clarification. The fad is in putting an official box in the organizational structure BEFORE understanding what has to be done to deploy better project management in an organization. Many organizations put into place  physical PMOs (desks with people)with no clear mandate and now official authority on anything. It is a top-down approach that just does not work, because deploying project management implies important cultural-organizational changes with many new roles and responsibilities. Even with formal authority, the work of these PMOs is often viewed as interference to business-as-usual (there has not been any cultural change coming simultaneously), is opposed and sabotaged, any of their directives are just not listened to and bypassed. After a few months, upper management just questions the use of this NEW BOX than does not seem to get along with anybody and has no measurable results for its justification. THEY then just close the <acronym title="Project Management Office">PMO</acronym> (the box) and project management as a core business process will have to wait the next crisis and the coming of a new upper management team. What is important, while evolving towards a project management culture, is to put in place facilitating tools, training, internal consulting, to SUPPORT people in their projects and help them to see by themselves the advantage of applying project management principles and putting in place true project teams working together. And if the organization has the resources, why not provide a &#8216;clearing house&#8217; for this facilitating work in the form of a PSO supporting project management rather than that of a <acronym title="Project Management Office">PMO</acronym> taking over (only in its mind) the management of projects.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Hal
        </title>
		<link>http://www.reformingprojectmanagement.com/2003/04/12/151/#comment-332</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2003/04/12/151/#comment-332</guid>
					<description>
        Bonjour Claude,

Thanks for the clarifications.  The interview was fun for me.

I hope you enjoy my next little project on TOC with two bloggers.  One I met in this forum, Frank Patrick.  The other, Joe Ely, is a past client and now a good friend.

This whole blogging scene has been wonderful for my professional development.

A bientot!
      </description>
		<content:encoded><![CDATA[<p>Bonjour Claude,</p>
<p>Thanks for the clarifications.  The interview was fun for me.</p>
<p>I hope you enjoy my next little project on <acronym title="Theory of Constraints; Eli Goldratt's insight on throughput">TOC</acronym> with two bloggers.  One I met in this forum, Frank Patrick.  The other, Joe Ely, is a past client and now a good friend.</p>
<p>This whole blogging scene has been wonderful for my professional development.</p>
<p>A bientot!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Frank Winters
        </title>
		<link>http://www.reformingprojectmanagement.com/2003/04/12/151/#comment-333</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2003/04/12/151/#comment-333</guid>
					<description>
        PMO, PSO ...
Are we talking about Programs? If so I think the PMO's time will come, allbeit with a different name. Programs are business initiatives -- if they are concieved correctly. If an organization wants to control corporate development, a PMO is needed. Wouldn't be nice if companies could control how the money was being spent from the top down. Projects that don't fit into a busines initiative, aka program, could be summerially canceled (off with their heads!) and costs controlled. This instead of the runnaway spending and projects with no business purpose that we see in major corporations today. But I guess I'm just a dreamer.......
      </description>
		<content:encoded><![CDATA[<p><acronym title="Project Management Office">PMO</acronym>, PSO &#8230;<br />
Are we talking about Programs? If so I think the <acronym title="Project Management Office">PMO</acronym>&#8217;s time will come, allbeit with a different name. Programs are business initiatives &#8212; if they are concieved correctly. If an organization wants to control corporate development, a <acronym title="Project Management Office">PMO</acronym> is needed. Wouldn&#8217;t be nice if companies could control how the money was being spent from the top down. Projects that don&#8217;t fit into a busines initiative, aka program, could be summerially canceled (off with their heads!) and costs controlled. This instead of the runnaway spending and projects with no business purpose that we see in major corporations today. But I guess I&#8217;m just a dreamer&#8230;&#8230;.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
