<?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>PMcrunch &#187; Search Results  &#187;  risks</title>
	<atom:link href="http://pmcrunch.com/search/risks/feed/rss2/" rel="self" type="application/rss+xml" />
	<link>http://pmcrunch.com</link>
	<description>Fresh perspectives on the world of project management</description>
	<lastBuildDate>Wed, 08 Feb 2012 04:24:49 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>What do Project Management, Six Sigma, Business Analysis, and ITIL  have in common?</title>
		<link>http://pmcrunch.com/project_management_process/what-do-project-management-six-sigma-business-analysis-and-itil-have-in-common/</link>
		<comments>http://pmcrunch.com/project_management_process/what-do-project-management-six-sigma-business-analysis-and-itil-have-in-common/#comments</comments>
		<pubDate>Thu, 09 Sep 2010 20:00:59 +0000</pubDate>
		<dc:creator>John Reiling</dc:creator>
				<category><![CDATA[Project Management Process]]></category>

		<guid isPermaLink="false">http://pmcrunch.com/?p=688</guid>
		<description><![CDATA[Project Management, Six Sigma, Business Analysis, and ITIL all provide domain frameworks, all have associated business certifications, all live largely in the ‘business’ versus technical realm, and all have a strong process orientation. But what does that mean to business professionals and organizations?  Here are some thoughts on implications based upon the ITIL framework. ]]></description>
		<wfw:commentRss>http://pmcrunch.com/project_management_process/what-do-project-management-six-sigma-business-analysis-and-itil-have-in-common/feed/</wfw:commentRss>
		<slash:comments>902</slash:comments>
		</item>
		<item>
		<title>Learning By Both Experience and Education</title>
		<link>http://pmcrunch.com/soft_skills/learning-by-both-experience-and-education/</link>
		<comments>http://pmcrunch.com/soft_skills/learning-by-both-experience-and-education/#comments</comments>
		<pubDate>Sun, 22 Nov 2009 11:39:53 +0000</pubDate>
		<dc:creator>maryjoy</dc:creator>
				<category><![CDATA[Soft Skills]]></category>
<category>enterpreneur</category><category>logical way</category><category>project management</category><category>small experiences</category><category>speed learning</category>
		<guid isPermaLink="false">http://pmcrunch.com/main/648/</guid>
		<description><![CDATA[We all want to learn more and indeed [tag-tec]“speed learning”[/tag-tec] is a requirement in today’s fast paced world. I recently heard an interesting quote from an entrepreneur who said that he looks it what he has learned as an entrepreneur and he realized that he already been taught that in business school but he wasn’t paying attention.]]></description>
		<wfw:commentRss>http://pmcrunch.com/soft_skills/learning-by-both-experience-and-education/feed/</wfw:commentRss>
		<slash:comments>862</slash:comments>
		</item>
		<item>
		<title>Incremental Changes Versus &#8220;Betting The Farm&#8221;</title>
		<link>http://pmcrunch.com/project_management_process/incremental-changes-versus-betting-the-farm/</link>
		<comments>http://pmcrunch.com/project_management_process/incremental-changes-versus-betting-the-farm/#comments</comments>
		<pubDate>Tue, 03 Nov 2009 04:00:48 +0000</pubDate>
		<dc:creator>bcosgrove</dc:creator>
				<category><![CDATA[Project Management Process]]></category>
<category>agile project management</category><category>change management</category><category>incremental changes</category><category>make changes</category><category>project scope</category><category>risk analysis</category>
		<guid isPermaLink="false">http://pmcrunch.com/project_management_process/incremental-changes-versus-betting-the-farm/</guid>
		<description><![CDATA[On our projects, and in our programs and project portfolios, we often struggle with how to make changes.&#160; From my own personal experience, the most challenging part of change management&#160;has always been the area of making incremental changes versus making wholesale major changes.&#160; Let&#8217;s take a look.&#160; My personal tendency is to favor incremental changes [...]]]></description>
		<wfw:commentRss>http://pmcrunch.com/project_management_process/incremental-changes-versus-betting-the-farm/feed/</wfw:commentRss>
		<slash:comments>1028</slash:comments>
		</item>
		<item>
		<title>Monitoring Employee Satisfaction &#8211; The Advantages, Considerations and Risks</title>
		<link>http://pmcrunch.com/project_management_process/monitoring-employee-satisfaction-the-advantages-considerations-and-risks/</link>
		<comments>http://pmcrunch.com/project_management_process/monitoring-employee-satisfaction-the-advantages-considerations-and-risks/#comments</comments>
		<pubDate>Thu, 09 Jul 2009 21:03:22 +0000</pubDate>
		<dc:creator>myarticlenetwork</dc:creator>
				<category><![CDATA[Project Management Process]]></category>

		<guid isPermaLink="false">http://pmcrunch.com/project_management_process/monitoring-employee-satisfaction-the-advantages-considerations-and-risks/</guid>
		<description><![CDATA[Although there are distinct advantages to conducting regular employee satisfaction surveys online to measuring employee satisfaction &#8211; there can also be risks. Documented here are the main advantages, considerations and the possible risks to conducting employee satisfaction surveys online. &#160; Advantages Identify Problems &#8211; Surveys are can be very effective in identify problems areas before [...]]]></description>
		<wfw:commentRss>http://pmcrunch.com/project_management_process/monitoring-employee-satisfaction-the-advantages-considerations-and-risks/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Sensible Incentivizing</title>
		<link>http://pmcrunch.com/project_management_process/sensible-incentivizing/</link>
		<comments>http://pmcrunch.com/project_management_process/sensible-incentivizing/#comments</comments>
		<pubDate>Thu, 14 May 2009 12:52:51 +0000</pubDate>
		<dc:creator>John Reiling</dc:creator>
				<category><![CDATA[Project Management Process]]></category>
<category>banking crisis</category><category>compensation structure</category><category>form of compensation</category><category>how people are incentivized</category><category>incentives</category><category>incentivizing</category><category>intangible incentives</category><category>network-building opportunities</category><category>organizational relationships</category><category>project managers</category><category>project success</category><category>risky loan portfolios</category><category>set of incentives</category><category>team members</category><category>value of individual contributions</category>
		<guid isPermaLink="false">http://pmcrunch.com/project_management_process/sensible-incentivizing/</guid>
		<description><![CDATA[Looking at lessons learned from the current economic crisis, one that stands out pertains to how people are incentivized in business. Banks with risky loan portfolios somewhere along the line had incentivized their people to fill their portofolios with these loans. Somewhere along the line, the incentives did not incorporate some of the risks involved. How does this play out in project and program management?]]></description>
		<wfw:commentRss>http://pmcrunch.com/project_management_process/sensible-incentivizing/feed/</wfw:commentRss>
		<slash:comments>45</slash:comments>
		</item>
		<item>
		<title>Communicating a Clear and Positive Way Ahead</title>
		<link>http://pmcrunch.com/project_management_process/communicating-a-clear-and-positive-way-ahead/</link>
		<comments>http://pmcrunch.com/project_management_process/communicating-a-clear-and-positive-way-ahead/#comments</comments>
		<pubDate>Tue, 10 Mar 2009 12:44:46 +0000</pubDate>
		<dc:creator>John Reiling</dc:creator>
				<category><![CDATA[Project Management Process]]></category>
<category>acceptance of our assumptions</category><category>alternatives</category><category>answer stakeholder questions</category><category>best plan</category><category>communicate</category><category>communicate with our stakeholders</category><category>courses of action</category><category>Project and program managers</category><category>solution-oriented</category>
		<guid isPermaLink="false">http://pmcrunch.com/project_management_process/communicating-a-clear-and-positive-way-ahead/</guid>
		<description><![CDATA[Project and program managers today are in a position of needing to grapple with many tough choices. We need to assess and re-assess our options and, in an almost tortuous way, develop a positive way ahead to communicate with our stakeholders. For us, the process of going through that struggle is important. But to our stakeholders, what is important is the positive way ahead that we have developed.]]></description>
		<wfw:commentRss>http://pmcrunch.com/project_management_process/communicating-a-clear-and-positive-way-ahead/feed/</wfw:commentRss>
		<slash:comments>691</slash:comments>
		</item>
		<item>
		<title>Beware The Programmatics Trap</title>
		<link>http://pmcrunch.com/project_management_process/beware-the-programmatics-trap/</link>
		<comments>http://pmcrunch.com/project_management_process/beware-the-programmatics-trap/#comments</comments>
		<pubDate>Fri, 06 Mar 2009 12:49:53 +0000</pubDate>
		<dc:creator>John Reiling</dc:creator>
				<category><![CDATA[Project Management Process]]></category>
<category>decision making</category><category>effective scope statement</category><category>estimates and risks</category><category>job activity</category><category>producing results</category><category>programmatics</category><category>Programmatics orientation</category><category>programmatics-oriented position</category><category>project management</category><category>project plan</category>
		<guid isPermaLink="false">http://pmcrunch.com/project_management_process/beware-the-programmatics-trap/</guid>
		<description><![CDATA[Many project management positions are just that -- positions managing projects. However, many other positions seemingly in project management are much more positions in programmatics. They involve tracking, reporting, working with metrics, and passing information on to decision makers. While, often, there is a need for these functions, there, often, also is not.]]></description>
		<wfw:commentRss>http://pmcrunch.com/project_management_process/beware-the-programmatics-trap/feed/</wfw:commentRss>
		<slash:comments>893</slash:comments>
		</item>
		<item>
		<title>3 Approaches for Project Management When Visibility Is Low</title>
		<link>http://pmcrunch.com/project_management_process/3-approaches-for-project-management-when-visibility-is-low/</link>
		<comments>http://pmcrunch.com/project_management_process/3-approaches-for-project-management-when-visibility-is-low/#comments</comments>
		<pubDate>Thu, 05 Mar 2009 12:46:59 +0000</pubDate>
		<dc:creator>John Reiling</dc:creator>
				<category><![CDATA[Project Management Process]]></category>
<category>Control expenditure</category><category>economic recovery</category><category>risk assessment</category><category>times of low visibility</category><category>tough times</category><category>use our instrumentation</category><category>visibility is low</category>
		<guid isPermaLink="false">http://pmcrunch.com/project_management_process/3-approaches-for-project-management-when-visibility-is-low/</guid>
		<description><![CDATA[These tough times are different from past recessions in that "visibility is low". What I mean by that is that it is not just a matter of seeing that sales had declined a certain amount, or that certain costs had reached a certain amount; it is not just that there is a general slimming or pruning of weaker competitors across the board. The problem is that it is very hard to predict with any reasonable level of certainty what is going to happen next and, thus, we find ourselves driving through our challenges "with low visibility".]]></description>
		<wfw:commentRss>http://pmcrunch.com/project_management_process/3-approaches-for-project-management-when-visibility-is-low/feed/</wfw:commentRss>
		<slash:comments>1099</slash:comments>
		</item>
		<item>
		<title>Right-Sizing 101</title>
		<link>http://pmcrunch.com/project_management_process/right-sizing-101/</link>
		<comments>http://pmcrunch.com/project_management_process/right-sizing-101/#comments</comments>
		<pubDate>Thu, 12 Feb 2009 12:43:32 +0000</pubDate>
		<dc:creator>John Reiling</dc:creator>
				<category><![CDATA[Project Management Process]]></category>
<category>business segment</category><category>customer profile</category><category>decrease in sales</category><category>downsizing</category><category>essential segments</category><category>general management</category><category>project decisions</category><category>project manager</category><category>resizing</category><category>right-size their businesses</category><category>Right-sizing</category><category>suggest alternatives</category><category>Thomas Watson</category>
		<guid isPermaLink="false">http://pmcrunch.com/project_management_process/right-sizing-101/</guid>
		<description><![CDATA[In today's economy, managers of all kinds are under pressure to right-size their businesses or business units. With the contraction of the economy, sales decreases trigger the need for rethinking, resizing, and reshaping throughout any organization. Projects and programs are no different. Let's take a look. ]]></description>
		<wfw:commentRss>http://pmcrunch.com/project_management_process/right-sizing-101/feed/</wfw:commentRss>
		<slash:comments>1426</slash:comments>
		</item>
		<item>
		<title>Measure Twice, Cut Once</title>
		<link>http://pmcrunch.com/project_management_process/measure-twice-cut-once/</link>
		<comments>http://pmcrunch.com/project_management_process/measure-twice-cut-once/#comments</comments>
		<pubDate>Tue, 20 Jan 2009 12:31:18 +0000</pubDate>
		<dc:creator>John Reiling</dc:creator>
				<category><![CDATA[Project Management Process]]></category>
<category>idea of planning</category><category>identifying the stakeholders</category><category>measure twice and cut once</category><category>need to communicate</category><category>stakeholder analysis</category>
		<guid isPermaLink="false">http://pmcrunch.com/project_management_process/measure-twice-cut-once/</guid>
		<description><![CDATA[When thinking about stakeholder analysis, I am reminded of the old carpenter's motto which is to "measure twice and cut once". The idea here in project management is to make sure you have clearly laid out what is to be done before beginning a project. Now this being said, there are many shades of grey.]]></description>
		<wfw:commentRss>http://pmcrunch.com/project_management_process/measure-twice-cut-once/feed/</wfw:commentRss>
		<slash:comments>653</slash:comments>
		</item>
	</channel>
</rss>
<!-- This Quick Cache file was built for (  www.pmcrunch.com/search/risks/feed/rss2/ ) in 0.49901 seconds, on Feb 11th, 2012 at 2:38 am UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 11th, 2012 at 3:38 am UTC -->
