# Software Estimates are not Targets

DevFeed: [Software Estimates are not Targets](<https://devfeed.tech/articles/software-estimates-are-not-targets-24943.md>)

Original publisher: [Read original article](<https://codeahoy.com/2016/05/14/software-estimates-are-not-targets/>)

Author: umer

Published: 2016-05-14T00:00:00Z

Content type: opinion

Language: en

Sources: [Code Ahoy - Articles](<https://devfeed.tech/sources/code-ahoy-articles.md>)

Topics: [Development](<https://devfeed.tech/topics/development.md>), [Software](<https://devfeed.tech/topics/software.md>), [code productivity](<https://devfeed.tech/topics/code-productivity.md>)

Tags: [blog-post](<https://devfeed.tech/tags/blog-post.md>), [development](<https://devfeed.tech/tags/development.md>), [software](<https://devfeed.tech/tags/software.md>), [software-development](<https://devfeed.tech/tags/software-development.md>)

## AI overview

This article argues that software estimates are necessary for planning, release timing, resource allocation, and go/no-go decisions. It explains that estimates are distinct from organizational targets and plans, which describe desired outcomes and the actions intended to achieve them.

## Source excerpt

Software estimation is a hard problem. So much so that in 2012, when Woody Zuill tweeted his blog post with the hashtag #NoEstimates, he set the software development community on fire. Everyone from discontented developers to seasoned software veterans flocked to the discussion on Twitter on either side of the debate. (You can read more about the #NoEstimates movement here.) In this post, let's try to answer the question whether we need estimates and then look at what software estimates are and more importantly what they aren't. Tom Demarco gave the following tongue-in-cheek definition of a software estimate: "An estimate is the most optimistic prediction that has a non-zero probability of coming true." Which brings me to my next point. Do We Need Estimates? The short answer is yes, we do. We need estimates for the following reasons: To know when something will be done. To provide a release date. To allocate cost, resources and people. To make go/no-go calls: pursue the development or kill the proposal. We need estimates to make decisions and estimates form the foundation of plans. Good estimates allow us to make sound decisions and to chart a course of action. What is an Estimate? Google gives the following definition of an estimate: roughly calculate or judge the value, number, quantity, or extent of. an approximate calculation or judgment of the value, number, quantity, or extent of something. Strictly speaking, the dictionary's definition is correct but the term has very different connotations in the software world. Estimates are frequently confused with organizational targets and plans. An organizational target is a desirable outcome that benefits the organization in one way or the other. It is an objective that the organization seeks. When you hear statements that sound similar to the following, immediately know that the speaker is talking about the organization's targets, not estimates: "The goal is to have the new feature released by May 19th all users." "We