Differences

This shows you the differences between two versions of the page.

--- where_did_this_estimation_approach_come_from [2019/01/14 14:50] – [Where Did This Estimation Approach Come From?] hpsamios
+++ where_did_this_estimation_approach_come_from [2020/06/02 14:22] – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== Where Did This Estimation Approach Come From? ======
-Ever wondered where the story point / relative sizing based estimating approach came from. It turns out there was significant amount of research into doing estimates, since this was considered such a core part of the software development process. The result is that this estimation approach has been validated by that research.
+Ever wondered where the story point / relative sizing based estimating approach came from. A lot of the thinking is based on the "Wideband Delphi" estimation method, a consensus-based technique for estimating effort. This, in turn, was derived from the Delphi method which was developed in the 1950-1960s at the RAND Corporation as a forecasting tool. It has since been adapted across many industries to estimate many kinds of tasks, ranging from statistical data collection results to sales and marketing forecasts.
-Looking at the approach
+In addition, it turns out there was significant amount of research into doing estimates, since this was considered such a core part of the software development process. The result is that this estimation approach has been validated by that research.
+Looking at the approach:
   * Those that do the work, estimate the work (1)
@@ Line 10: / Line 12: @@
   * Combining individual estimates through group discussion yield better estimates (6, 7)
-The numbers refer to the following References:
+The numbers refer to the following references:
   - Jørgensen, Magne. 2004. A Review of Studies on Expert Estimation of Software Development Effort.
@@ Line 24: / Line 26: @@
 In addition, this approach leads to:
-  * Emphasizing relative rather than absolute estimates, which means that you can estimate very quickly. People are very good at deciding whether something is bigger or smaller than something else (relative size estimates), but are terrible at determining how big it is (absolute estimates). You will often see teams that can produce 20, 30 even 40 estimates in an hour with improved data and far less wastage associated with the process.
+  * Emphasizing relative rather than absolute estimates, which means that you can estimate very quickly. People are very good at deciding whether something is bigger or smaller than something else (relative size estimates), but are terrible at determining how big it is (absolute estimates). You will often see Teams that can produce 20, 30 even 40 estimates in an hour with improved data and far less wastage associated with the process.
-  * Estimates are constrained to a set of values so that we don’t waste time on meaningless arguments
+  * Estimates are constrained to a set of values so that we don’t waste time on meaningless arguments.
-  * Everyone’s opinion is heard
+  * Everyone’s opinion is heard.
   * Its fun! (or at least more fun than the old way)