<?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: Don&#8217;t Screw this Up:  Alignment</title>
	<atom:link href="http://pmstudent.com/dont-screw-this-up-alignment/feed/" rel="self" type="application/rss+xml" />
	<link>http://pmstudent.com/dont-screw-this-up-alignment/</link>
	<description>Helping new and aspiring project managers reach their career goals!</description>
	<lastBuildDate>Sun, 20 May 2012 01:38:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Josh Nankivel</title>
		<link>http://pmstudent.com/dont-screw-this-up-alignment/#comment-16934</link>
		<dc:creator>Josh Nankivel</dc:creator>
		<pubDate>Wed, 18 Nov 2009 02:35:23 +0000</pubDate>
		<guid isPermaLink="false">http://pmstudent.com/?p=4581#comment-16934</guid>
		<description>I went to my local PMI chapter&#039;s lunch meeting today and got to chat with a former classmate of mine.  Aaron brought up something in discussion that got me thinking.

In the quest for alignment, many organizations take a top-down approach and try to implement rigid processes across the organization for managing projects.  And many try to do it overnight.

I&#039;d like to stress that if a project environment is not aligned, the program as a whole isn&#039;t going to change overnight.  It&#039;s better in my experience to put together a long-term transition plan with the right people involved, with clear milestones that move the whole organization towards the goal of alignment.

Otherwise, you usually end up with a half-ass implementation of something that doesn&#039;t really accomplish much of anything and just pisses a bunch of people off!  When that happens, your best staff leave first because they have options.</description>
		<content:encoded><![CDATA[<p>I went to my local PMI chapter&#8217;s lunch meeting today and got to chat with a former classmate of mine.  Aaron brought up something in discussion that got me thinking.</p>
<p>In the quest for alignment, many organizations take a top-down approach and try to implement rigid processes across the organization for managing projects.  And many try to do it overnight.</p>
<p>I&#8217;d like to stress that if a project environment is not aligned, the program as a whole isn&#8217;t going to change overnight.  It&#8217;s better in my experience to put together a long-term transition plan with the right people involved, with clear milestones that move the whole organization towards the goal of alignment.</p>
<p>Otherwise, you usually end up with a half-ass implementation of something that doesn&#8217;t really accomplish much of anything and just pisses a bunch of people off!  When that happens, your best staff leave first because they have options.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh Nankivel</title>
		<link>http://pmstudent.com/dont-screw-this-up-alignment/#comment-25703</link>
		<dc:creator>Josh Nankivel</dc:creator>
		<pubDate>Wed, 18 Nov 2009 02:35:00 +0000</pubDate>
		<guid isPermaLink="false">http://pmstudent.com/?p=4581#comment-25703</guid>
		<description>I went to my local PMI chapter&#039;s lunch meeting today and got to chat with a former classmate of mine.  Aaron brought up something in discussion that got me thinking.

In the quest for alignment, many organizations take a top-down approach and try to implement rigid processes across the organization for managing projects.  And many try to do it overnight.

I&#039;d like to stress that if a project environment is not aligned, the program as a whole isn&#039;t going to change overnight.  It&#039;s better in my experience to put together a long-term transition plan with the right people involved, with clear milestones that move the whole organization towards the goal of alignment.

Otherwise, you usually end up with a half-ass implementation of something that doesn&#039;t really accomplish much of anything and just pisses a bunch of people off!  When that happens, your best staff leave first because they have options.</description>
		<content:encoded><![CDATA[<p>I went to my local PMI chapter&#8217;s lunch meeting today and got to chat with a former classmate of mine.  Aaron brought up something in discussion that got me thinking.</p>
<p>In the quest for alignment, many organizations take a top-down approach and try to implement rigid processes across the organization for managing projects.  And many try to do it overnight.</p>
<p>I&#8217;d like to stress that if a project environment is not aligned, the program as a whole isn&#8217;t going to change overnight.  It&#8217;s better in my experience to put together a long-term transition plan with the right people involved, with clear milestones that move the whole organization towards the goal of alignment.</p>
<p>Otherwise, you usually end up with a half-ass implementation of something that doesn&#8217;t really accomplish much of anything and just pisses a bunch of people off!  When that happens, your best staff leave first because they have options.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

