User Tools

Site Tools


where_did_this_estimation_approach_come_from

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
where_did_this_estimation_approach_come_from [2019/01/15 09:35] – Added wideband delphi hpsamioswhere_did_this_estimation_approach_come_from [2021/12/08 13:51] (current) – Added references hans
Line 12: Line 12:
   * Combining individual estimates through group discussion yield better estimates (6, 7)   * 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.   - 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:  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)   * Its fun! (or at least more fun than the old way)
  
Line 37: Line 37:
   * [[why_do_we_use_story_points_instead_of_hours|Why Do We Use Story Points Instead of Hours or Days?]]   * [[why_do_we_use_story_points_instead_of_hours|Why Do We Use Story Points Instead of Hours or Days?]]
   * [[what_is_the_purpose_of_estimation|What is the Purpose of Estimation?]]   * [[what_is_the_purpose_of_estimation|What is the Purpose of Estimation?]]
 +  * [[https://www.mountaingoatsoftware.com/blog/why-the-fibonacci-sequence-works-well-for-estimating|Why the Fibonacci Sequence Works for Estimating]] - Weber’s Law approach from Mike Cohn
 +  * [[http://www.yakyma.com/2012/05/why-progressive-estimation-scale-is-so.html|Why Progressive Estimation Scale is So Efficient]] - Information theory approach from Alex Yakyma
  
 {{tag>Team Estimates Forecast FAQ Points EstimationApproach}} {{tag>Team Estimates Forecast FAQ Points EstimationApproach}}
/home/hpsamios/hanssamios.com/dokuwiki/data/attic/where_did_this_estimation_approach_come_from.1547573711.txt.gz · Last modified: 2020/06/02 14:32 (external edit)