The default use of an "estimate-driven" approach is pervasive in software development efforts, and while estimates can be useful, it is worthwhile to scrutinize our use of estimates for cost, time, and effort, and to seek better ways to manage software development projects. We say we depend on estimates to make important decisions, and yet we’re often disappointed by the results.
 
We'll explore the purpose and use of estimates in the management of software development efforts, and consider possible ways to work without trying to predict the future. There are a number of things to explore and many questions to ask. For example, are we getting a reasonable benefit from estimates? Is there a way to prove that estimates are helping us make good decisions? Do we really need estimates for all the things we are currently using them for? Is it possible to manage software development projects without these estimates, or at least with fewer estimates?
 
We’ll examine the nature of estimates in software development projects and look at a few ideas about moving beyond estimates.