Difference between revisions of "Estimate"
Jump to navigation
Jump to search
(+= http://www.infoq.com/resource/minibooks/emag-agile-estimation/en/pdf/Agile-Project-Estimation-and-Planning-eMag.pdf) |
(See {{p|plastic plan}}.) |
||
| Line 8: | Line 8: | ||
*http://softwaredevelopmenttoday.blogspot.co.nz/2012/01/story-points-considered-harmful-or-why.html | *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 | *http://www.infoq.com/resource/minibooks/emag-agile-estimation/en/pdf/Agile-Project-Estimation-and-Planning-eMag.pdf | ||
See {{p|plastic plan}}. | |||
Revision as of 15:07, 7 September 2014
- It’s better to be roughly right than precisely wrong
- → 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.