# IT:AD:Design:Estimates #



<callout type="Navigation" class="small">

* [[../|(UP)]]
{{indexmenu>.#2|nsort tsort}}

* **[[IT/AD/Design/Estimates/Checklists/]]**: checklist of AD tasks, used to inform the meta [[IT/PM/Estimates/Checklists|IT/PM/Estimates/Checklists]]
* [[IT/AD/Design/Estimates/Errors/]]
* [[IT/AD/Design/Estimates/Tools/]]
* See also:
    * [[IT/PM/Processes/Estimates/]]: How a Manager sees the same estimates.


</callout>


<panel title="Summary">

Good estimates minimize risk of failure (not to be confused with get rid of risk). 

Yet, as a whole, our industry is absolutely abysmal at correctly estimating the size of projects.


</panel>


## Resources ##
* Are they ever going to get any good?
    * http://gigamonkeys.wordpress.com/2007/04/26/estimation-considered-harmful/
* EXCELLENT: [http://agile.csc.ncsu.edu/SEMaterials/EstimatingPlanning.pdf](http://agile.csc.ncsu.edu/SEMaterials/EstimatingPlanning.pdf)
* [http://okapya.com/rekall/why-use-triangulation](http://okapya.com/rekall/why-use-triangulation)
* [http://www.mountaingoatsoftware.com/books/agile-estimating-and-planning/](http://www.mountaingoatsoftware.com/books/agile-estimating-and-planning/)
* http://www.matvoz.com/blog/2013/10/let-me-tell-you-why-the-last-20-of-work-takes-the-same-amount-of-time-as-the-first-80/
* http://www.infoq.com/articles/software-development-effort-estimation