Differences

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

--- where_did_this_estimation_approach_come_from [2019/01/15 09:35] – Added wideband delphi hpsamios
+++ where_did_this_estimation_approach_come_from [2020/06/02 14:22] – external edit 127.0.0.1
@@ Line 12: / 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 26: / 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)