Software development effort estimation: Difference between revisions

Content deleted Content added
GreenC bot (talk | contribs)
Rescued 2 archive links. Wayback Medic 2.5
Line 237:
==Humor==
The chronic underestimation of development effort has led to the coinage and popularity of numerous humorous adages, such as ironically referring to a task as a "[[small matter of programming]]" (when much effort is likely required), and citing laws about underestimation:
* [[Ninety-ninetyNinety–ninety rule]]:
{{quotation |<!-- PLEASE DON'T CHANGE THIS QUOTE WITHOUT CHECKING THE ORIGINAL SOURCE! THE %'S ARE NOT SUPPOSED TO TOTAL 100%! -->The first 90 percent of the code accounts for the first 90 percent of the development time. The remaining 10 percent of the code accounts for the other 90<!-- YES THIS TOTALS 180%! THIS IS NOT AN ERROR! --> percent of the development time.<ref name="Bentley1985">{{cite journal|last= Bentley|first= Jon|year= 1985|title= Programming pearls|journal= Communications of the ACM|volume= 28|issue= 9|pages= 896–901|issn= 0001-0782|doi= 10.1145/4284.315122|s2cid= 5832776|format= fee required}}</ref> |Tom Cargill|[[Bell Labs]]}}
* [[Hofstadter's law]]:
Line 247:
{{quotation|What one programmer can do in one month, two programmers can do in two months.|[[Fred Brooks]]|
}} Adding to the fact that estimating development efforts is hard, it's worth stating that assigning more resources doesn't always help.
 
 
==Comparison of development estimation software==