<?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: Estimating Effort: Part 3</title>
	<atom:link href="http://pmstudent.com/estimating-effort-part-3/feed/" rel="self" type="application/rss+xml" />
	<link>http://pmstudent.com/estimating-effort-part-3/</link>
	<description>Helping new and aspiring project managers reach their career goals!</description>
	<lastBuildDate>Wed, 08 Feb 2012 14:16:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Project Estimation Methods</title>
		<link>http://pmstudent.com/estimating-effort-part-3/#comment-26674</link>
		<dc:creator>Project Estimation Methods</dc:creator>
		<pubDate>Sun, 14 Nov 2010 18:48:31 +0000</pubDate>
		<guid isPermaLink="false">http://pmstudent.com/?p=1461#comment-26674</guid>
		<description>[...] Estimating Effort: Part 3 [...]</description>
		<content:encoded><![CDATA[<p>[...] Estimating Effort: Part 3 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KW Variant 3</title>
		<link>http://pmstudent.com/estimating-effort-part-3/#comment-26217</link>
		<dc:creator>KW Variant 3</dc:creator>
		<pubDate>Sun, 10 Oct 2010 08:54:00 +0000</pubDate>
		<guid isPermaLink="false">http://pmstudent.com/?p=1461#comment-26217</guid>
		<description>
Firstly you will need to check the Fork and Shock sag: this is the amount the forks and rear shock settle under load. To measure it do the following: push down on the forks a number of times to settle them, then mark the stanchion with a felt pen or put a cable tie where the dust seal is sitting. Next ask some for help to lift on the bars so the front wheel is just off the ground and measure the amount the forks have traveled down. This is the static sag (or unladen sag), This can be changed by adjusting the spring preload (more preload = less sag). Repeat the same process for the rear, this time measuring the distance from the wheel spindle to a fixed point on the tail. Now you are ready to begin setting up your suspension. The key is to do it a little at a time and make notes as you go. For road riding start with the wet track settings and work from there.
</description>
		<content:encoded><![CDATA[<p>Firstly you will need to check the Fork and Shock sag: this is the amount the forks and rear shock settle under load. To measure it do the following: push down on the forks a number of times to settle them, then mark the stanchion with a felt pen or put a cable tie where the dust seal is sitting. Next ask some for help to lift on the bars so the front wheel is just off the ground and measure the amount the forks have traveled down. This is the static sag (or unladen sag), This can be changed by adjusting the spring preload (more preload = less sag). Repeat the same process for the rear, this time measuring the distance from the wheel spindle to a fixed point on the tail. Now you are ready to begin setting up your suspension. The key is to do it a little at a time and make notes as you go. For road riding start with the wet track settings and work from there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Glen B. Alleman</title>
		<link>http://pmstudent.com/estimating-effort-part-3/#comment-4984</link>
		<dc:creator>Glen B. Alleman</dc:creator>
		<pubDate>Thu, 08 Jan 2009 17:03:52 +0000</pubDate>
		<guid isPermaLink="false">http://pmstudent.com/?p=1461#comment-4984</guid>
		<description>Bill,
Matahematically the triangle is best suited in the absensce of underlying information. It possess the least cummulant divergence for forecasting likley values drawn by a random number generator. You do not want the numbers to be correlated when produces them for modeling.
If the population statistics are known - cummulatants known - than other distributions can be used. 
The paper at the SPE confernce concludes the order of asking the high, low and most likley has statistically signifcant differences. These estimates are made by subject matter experts - like the effort or duration should be.

Also, in our A&amp;D work we ask for the duration of the workpackage and its work elements first, from the subject mater experts. Then we ask for the labor loading needed. This we we get a bounded end to end duration early in the Basis of Estimate process, that can be founded on previous work and define the pre-conditions for holding that schedule. The trouble with IT is they never seem to have any credible estimates of duration or effort, since the development of software is Ad Hoc process with little or no modeling from past performance. Even &quot;new&quot; development in A&amp;D has parameteric modeling. Trying to introduce that into corporate IT is a bust, they simply don&#039;t have the understanding of why or how this is a benefit. I blame this entirely on the agile community.
For embedded SW and ground system in defense, a customer would NEVER take an estimate that did not have some kind of parametric modeling. SEER, Price-S, and COCOMO models are mandated.

I&#039;ll locate the paper in the archive and send it.</description>
		<content:encoded><![CDATA[<p>Bill,<br />
Matahematically the triangle is best suited in the absensce of underlying information. It possess the least cummulant divergence for forecasting likley values drawn by a random number generator. You do not want the numbers to be correlated when produces them for modeling.<br />
If the population statistics are known &#8211; cummulatants known &#8211; than other distributions can be used.<br />
The paper at the SPE confernce concludes the order of asking the high, low and most likley has statistically signifcant differences. These estimates are made by subject matter experts &#8211; like the effort or duration should be.</p>
<p>Also, in our A&amp;D work we ask for the duration of the workpackage and its work elements first, from the subject mater experts. Then we ask for the labor loading needed. This we we get a bounded end to end duration early in the Basis of Estimate process, that can be founded on previous work and define the pre-conditions for holding that schedule. The trouble with IT is they never seem to have any credible estimates of duration or effort, since the development of software is Ad Hoc process with little or no modeling from past performance. Even &#8220;new&#8221; development in A&amp;D has parameteric modeling. Trying to introduce that into corporate IT is a bust, they simply don&#8217;t have the understanding of why or how this is a benefit. I blame this entirely on the agile community.<br />
For embedded SW and ground system in defense, a customer would NEVER take an estimate that did not have some kind of parametric modeling. SEER, Price-S, and COCOMO models are mandated.</p>
<p>I&#8217;ll locate the paper in the archive and send it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Glen B. Alleman</title>
		<link>http://pmstudent.com/estimating-effort-part-3/#comment-24648</link>
		<dc:creator>Glen B. Alleman</dc:creator>
		<pubDate>Thu, 08 Jan 2009 17:03:00 +0000</pubDate>
		<guid isPermaLink="false">http://pmstudent.com/?p=1461#comment-24648</guid>
		<description>Bill,
Matahematically the triangle is best suited in the absensce of underlying information. It possess the least cummulant divergence for forecasting likley values drawn by a random number generator. You do not want the numbers to be correlated when produces them for modeling.
If the population statistics are known - cummulatants known - than other distributions can be used. 
The paper at the SPE confernce concludes the order of asking the high, low and most likley has statistically signifcant differences. These estimates are made by subject matter experts - like the effort or duration should be.

Also, in our A&amp;D work we ask for the duration of the workpackage and its work elements first, from the subject mater experts. Then we ask for the labor loading needed. This we we get a bounded end to end duration early in the Basis of Estimate process, that can be founded on previous work and define the pre-conditions for holding that schedule. The trouble with IT is they never seem to have any credible estimates of duration or effort, since the development of software is Ad Hoc process with little or no modeling from past performance. Even &quot;new&quot; development in A&amp;D has parameteric modeling. Trying to introduce that into corporate IT is a bust, they simply don&#039;t have the understanding of why or how this is a benefit. I blame this entirely on the agile community.
For embedded SW and ground system in defense, a customer would NEVER take an estimate that did not have some kind of parametric modeling. SEER, Price-S, and COCOMO models are mandated.

I&#039;ll locate the paper in the archive and send it.</description>
		<content:encoded><![CDATA[<p>Bill,<br />
Matahematically the triangle is best suited in the absensce of underlying information. It possess the least cummulant divergence for forecasting likley values drawn by a random number generator. You do not want the numbers to be correlated when produces them for modeling.<br />
If the population statistics are known &#8211; cummulatants known &#8211; than other distributions can be used.<br />
The paper at the SPE confernce concludes the order of asking the high, low and most likley has statistically signifcant differences. These estimates are made by subject matter experts &#8211; like the effort or duration should be.</p>
<p>Also, in our A&amp;D work we ask for the duration of the workpackage and its work elements first, from the subject mater experts. Then we ask for the labor loading needed. This we we get a bounded end to end duration early in the Basis of Estimate process, that can be founded on previous work and define the pre-conditions for holding that schedule. The trouble with IT is they never seem to have any credible estimates of duration or effort, since the development of software is Ad Hoc process with little or no modeling from past performance. Even &#8220;new&#8221; development in A&amp;D has parameteric modeling. Trying to introduce that into corporate IT is a bust, they simply don&#8217;t have the understanding of why or how this is a benefit. I blame this entirely on the agile community.<br />
For embedded SW and ground system in defense, a customer would NEVER take an estimate that did not have some kind of parametric modeling. SEER, Price-S, and COCOMO models are mandated.</p>
<p>I&#8217;ll locate the paper in the archive and send it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Duncan</title>
		<link>http://pmstudent.com/estimating-effort-part-3/#comment-4980</link>
		<dc:creator>Bill Duncan</dc:creator>
		<pubDate>Thu, 08 Jan 2009 12:48:24 +0000</pubDate>
		<guid isPermaLink="false">http://pmstudent.com/?p=1461#comment-4980</guid>
		<description>Glen --

Thanks for the references. I will try to track them down. I found the Navy experiment interesting, and the results in contrast to some work done at the Texas Department of Prisons where they found that a triangular distribution was the most accurate representation of costs for their projects.

In the next article, I&#039;ll deal with some of the issues you raise.

And I love your example of Cody and Bermuda!

Duncan</description>
		<content:encoded><![CDATA[<p>Glen &#8211;</p>
<p>Thanks for the references. I will try to track them down. I found the Navy experiment interesting, and the results in contrast to some work done at the Texas Department of Prisons where they found that a triangular distribution was the most accurate representation of costs for their projects.</p>
<p>In the next article, I&#8217;ll deal with some of the issues you raise.</p>
<p>And I love your example of Cody and Bermuda!</p>
<p>Duncan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Duncan</title>
		<link>http://pmstudent.com/estimating-effort-part-3/#comment-24647</link>
		<dc:creator>Bill Duncan</dc:creator>
		<pubDate>Thu, 08 Jan 2009 12:48:00 +0000</pubDate>
		<guid isPermaLink="false">http://pmstudent.com/?p=1461#comment-24647</guid>
		<description>Glen --

Thanks for the references. I will try to track them down. I found the Navy experiment interesting, and the results in contrast to some work done at the Texas Department of Prisons where they found that a triangular distribution was the most accurate representation of costs for their projects.

In the next article, I&#039;ll deal with some of the issues you raise.

And I love your example of Cody and Bermuda!

Duncan</description>
		<content:encoded><![CDATA[<p>Glen &#8211;</p>
<p>Thanks for the references. I will try to track them down. I found the Navy experiment interesting, and the results in contrast to some work done at the Texas Department of Prisons where they found that a triangular distribution was the most accurate representation of costs for their projects.</p>
<p>In the next article, I&#8217;ll deal with some of the issues you raise.</p>
<p>And I love your example of Cody and Bermuda!</p>
<p>Duncan</p>
]]></content:encoded>
	</item>
</channel>
</rss>

