Difference between revisions of "Estimate"
Jump to navigation
Jump to search
(quotes++) |
m (Text++) |
||
| Line 2: | Line 2: | ||
{{quote|It’s better to be roughly right than precisely wrong|Maynard Keynes}} | {{quote|It’s better to be roughly right than precisely wrong|Maynard Keynes}} | ||
We | We keep on estimating and planning according to those estimates, expecting to meet deadlines and firing the {{p|wise fool}}s that question the practice, and report the actual numbers that are not accepted by management. However… | ||
{{quote|Insanity: Doing the same thing over and over and expecting different results.|Albert Einstein}} | {{quote|Insanity: Doing the same thing over and over and expecting different results.|Albert Einstein}} | ||
Revision as of 16:58, 7 September 2014
- In preparing for [projects] I have always found that [estimates] are useless, but [estimating] is indispensable.
- It’s better to be roughly right than precisely wrong
We keep on estimating and planning according to those estimates, expecting to meet deadlines and firing the wise fools that question the practice, and report the actual numbers that are not accepted by management. However…
- Insanity: Doing the same thing over and over and expecting different results.
- → metrics drive behavior
- → relative estimation
- http://www.djaa.com/noestimates-beef-and-agiles-trojan-horse
- #noestimates
- http://en.wikipedia.org/wiki/Probabilistic_method
- http://www.infoq.com/articles/software-development-effort-estimation
- http://softwaredevelopmenttoday.blogspot.co.nz/2012/01/story-points-considered-harmful-or-why.html
- http://www.infoq.com/resource/minibooks/emag-agile-estimation/en/pdf/Agile-Project-Estimation-and-Planning-eMag.pdf
See plastic plan.