Difference between revisions of "Estimate"
Jump to navigation
Jump to search
(See {{p|plastic plan}}.) |
(quotes++) |
||
| Line 1: | Line 1: | ||
{{quote|In preparing for [projects] I have always found that [estimates] are useless, but [estimating] is indispensable.|General Dwight D. Eisenhower}} | |||
{{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 beat ourselves up in post-implementation reviews and tell ourselves to just try become better in estimating; However… | |||
{{quote|Insanity: Doing the same thing over and over and expecting different results.|Albert Einstein}} | |||
*→ {{p|metrics drive behavior}} | *→ {{p|metrics drive behavior}} | ||
*→ {{p|relative estimation}} | *→ {{p|relative estimation}} | ||
Revision as of 16:56, 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 beat ourselves up in post-implementation reviews and tell ourselves to just try become better in estimating; 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.