<?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>Mark Woeppel on Management and Execution &#187; project scheduling</title>
	<atom:link href="http://pinnacle-strategies.com/blog/tag/project-scheduling/feed/" rel="self" type="application/rss+xml" />
	<link>http://pinnacle-strategies.com/blog</link>
	<description>I&#039;m writing about getting things done faster and more effectively.  Sometimes I&#039;ll write about other things.</description>
	<lastBuildDate>Sun, 06 Jun 2010 16:21:26 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Probabilistic Project Scheduling = Shorter Project Lead Times</title>
		<link>http://pinnacle-strategies.com/blog/2009/06/probabilistic-project-scheduling-shorter-project-lead-times/</link>
		<comments>http://pinnacle-strategies.com/blog/2009/06/probabilistic-project-scheduling-shorter-project-lead-times/#comments</comments>
		<pubDate>Fri, 19 Jun 2009 02:53:56 +0000</pubDate>
		<dc:creator>Mark Woeppel</dc:creator>
				<category><![CDATA[Critical Chain]]></category>
		<category><![CDATA[project planning]]></category>
		<category><![CDATA[project scheduling]]></category>

		<guid isPermaLink="false">http://pinnacle-strategies.com/blog/?p=143</guid>
		<description><![CDATA[Probabilistic project scheduling uses an understanding of the variation in project tasks and the project environment (project risks) to make a quantitative prediction of a range of project outcomes. Instead of providing a fixed date to answer a question such as “When is first oil?” probabilistic scheduling provides a range of answers of the type, [...]]]></description>
			<content:encoded><![CDATA[<p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-family: Candara; font-size: small;">Probabilistic project scheduling uses an understanding of the variation in project tasks and the project environment (project risks) to make a quantitative prediction of a range of project outcomes. Instead of providing a fixed date to answer a question such as “When is first oil?” probabilistic scheduling provides a range of answers of the type, “There is a 50% chance of achieving first oil by date x or sooner, and a 90% chance of achieving it by date y or sooner.” </span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-family: Candara; font-size: small;">A more general application of probabilistic planning also considers the range of project costs and returns. This evaluation focused on the range of outcomes for key project dates, such as first oil. Quantifying the range and probability of outcomes can aid project planning and decision-making.</span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-family: Candara; font-size: small;">Probabilistic scheduling provides a method to quantify the risk management process. Quantifying the impact of potential risks improves decision-making affecting the control of those risks, and potentially on the overall financial viability of the project. It specifically aids the upfront recognition of critical issues and proactive management of those issues.</span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-family: Candara; font-size: small;">So how does better planning result in shorter project lead times?  </span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-family: Candara; font-size: small;">First of all, there are fewer surprises.  Having done a proper job of evaluating project risk and task durations, you&#8217;re prepared to deal with the &#8220;murphys&#8221; that always occur during project execution.  Since you&#8217;ve already prepared, you can respond much quicker, without wasting time.</span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-family: Candara; font-size: small;">Second, a good project plan moves these potential risk events off the critical path (if possible!).  By moving risk events off the path that determines project delivery, eliminating disruption to your deliveries.  That doesn&#8217;t happen without planning.</span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-family: Candara; font-size: small;">Third, the tasks themselves are stripped of the safety that most project plans have, with all task safety aggregated at the end of the critical chain.  Saftey aggregation allows you to manage the safety as a project level item, rather than letting it be dispersed to every resource in your project.  That means that you need less, and the overall project duration is shorter with greater certainty of completion on time.</span></p>
<p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-family: Candara; font-size: small;">Ok, I have a white paper that explains this much more.  Get it <a href="http://pinnacle-strategies.com/Register1.htm" target="_blank">here</a>.</span></p>
]]></content:encoded>
			<wfw:commentRss>http://pinnacle-strategies.com/blog/2009/06/probabilistic-project-scheduling-shorter-project-lead-times/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
