<?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/"
	xmlns:series="http://unfoldingneurons.com/"
		>
<channel>
	<title>Comments on: Making projects work: project change and perceptions of failure</title>
	<atom:link href="http://www.pm4girls.elizabeth-harrin.com/2009/06/making-projects-work-project-change-and-perceptions-of-failure/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pm4girls.elizabeth-harrin.com/2009/06/making-projects-work-project-change-and-perceptions-of-failure/</link>
	<description>Project Management musings for one and all</description>
	<lastBuildDate>Thu, 02 Feb 2012 22:04:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Pradeep Bhanot</title>
		<link>http://www.pm4girls.elizabeth-harrin.com/2009/06/making-projects-work-project-change-and-perceptions-of-failure/comment-page-1/#comment-223153</link>
		<dc:creator>Pradeep Bhanot</dc:creator>
		<pubDate>Wed, 10 Jun 2009 08:35:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.pm4girls.elizabeth-harrin.com/?p=905#comment-223153</guid>
		<description>I liked the point Melanie made on focusing on accepting change being the norm for project requirements. I have seen some individuals take this a step further in formalizing the project change management process, by considering each change as a “defect” and engaging a well defined incident and change management process, whether it be a change to scope, requirement document or timeline. This is especially applicable to the iterative nature of agile segments of a project.   

I also agree that IT projects invariably lead to a business benefit, so why belittle them with an “IT project” label.

The PMO having a variety of methodologies to apply depending on need of a specific project.</description>
		<content:encoded><![CDATA[<p><span class='eg-image' style='float:right; margin-left:0px; width:40px' ><a rel='external nofollow' href='http://community.ca.com/blogs/ppm/'><img alt='' src='http://1.gravatar.com/avatar/3cd3466688374d75df104082ade6e64f?s=40&amp;d=http%3A%2F%2Fwww.pm4girls.elizabeth-harrin.com%2Ffavicon.ico%3Fs%3D40&amp;r=G' class='avatar avatar-40 photo' height='40' width='40' /></a></span>I liked the point Melanie made on focusing on accepting change being the norm for project requirements. I have seen some individuals take this a step further in formalizing the project change management process, by considering each change as a “defect” and engaging a well defined incident and change management process, whether it be a change to scope, requirement document or timeline. This is especially applicable to the iterative nature of agile segments of a project.   </p>
<p>I also agree that IT projects invariably lead to a business benefit, so why belittle them with an “IT project” label.</p>
<p>The PMO having a variety of methodologies to apply depending on need of a specific project.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Raj Menon</title>
		<link>http://www.pm4girls.elizabeth-harrin.com/2009/06/making-projects-work-project-change-and-perceptions-of-failure/comment-page-1/#comment-222782</link>
		<dc:creator>Raj Menon</dc:creator>
		<pubDate>Tue, 09 Jun 2009 04:48:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.pm4girls.elizabeth-harrin.com/?p=905#comment-222782</guid>
		<description>Very informative discussion. I really liked the part where Melanie talks about Program Management and the mindset has to change to &quot;move things around&quot; to manage keeping business objective in mind rather than project objective. Paul Major also touched upon an important distinction of Program Vs. Project Mgmt. Being a Program Mgr myself, it is very educational and reassuring. Can&#039;t wait for Part 2, Elizabeth.</description>
		<content:encoded><![CDATA[<p><span class='eg-image' style='float:right; margin-left:0px; width:40px' ><a rel='external nofollow' href='http://www.lap31.com'><img alt='' src='http://0.gravatar.com/avatar/00d8085ed0b02e607f4a8137151660f2?s=40&amp;d=http%3A%2F%2Fwww.pm4girls.elizabeth-harrin.com%2Ffavicon.ico%3Fs%3D40&amp;r=G' class='avatar avatar-40 photo' height='40' width='40' /></a></span>Very informative discussion. I really liked the part where Melanie talks about Program Management and the mindset has to change to &#8220;move things around&#8221; to manage keeping business objective in mind rather than project objective. Paul Major also touched upon an important distinction of Program Vs. Project Mgmt. Being a Program Mgr myself, it is very educational and reassuring. Can&#8217;t wait for Part 2, Elizabeth.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

