In software development, effort estimation is the process of predicting the most realistic amount of effort (expressed in terms of person-hours or money) required to develop or maintain software based on incomplete, uncertain and noisy input. Effort estimates may be used as input to project plans, iteration plans, budgets, investment analyses, pricing processes and bidding rounds.^{[1]}
Published surveys on estimation practice suggest that expert estimation is the dominant strategy when estimating software development effort.^{[2]}
Typically, effort estimates are over-optimistic and there is a strong over-confidence in their accuracy. The mean effort overrun seems to be about 30% and not decreasing over time. For a review of effort estimation error surveys, see.^{[3]} However, the measurement of estimation error is problematic, see Assessing the accuracy of estimates. The strong overconfidence in the accuracy of the effort estimates is illustrated by the finding that, on average, if a software professional is 90% confident or "almost sure" to include the actual effort in a minimum-maximum interval, the observed frequency of including the actual effort is only 60-70%.^{[4]}
Currently the term "effort estimate" is used to denote as different concepts such as most likely use of effort (modal value), the effort that corresponds to a probability of 50% of not exceeding (median), the planned effort, the budgeted effort or the effort used to propose a bid or price to the client. This is believed to be unfortunate, because communication problems may occur and because the concepts serve different goals.^{[5]}^{[6]}
Software researchers and practitioners have been addressing the problems of effort estimation for software development projects since at least the 1960s; see, e.g., work by Farr ^{[7]}^{[8]} and Nelson.^{[9]}
Most of the research has focused on the construction of formal software effort estimation models. The early models were typically based on regression analysis or mathematically derived from theories from other domains. Since then a high number of model building approaches have been evaluated, such as approaches founded on case-based reasoning, classification and regression trees, simulation, neural networks, Bayesian statistics, lexical analysis of requirement specifications, genetic programming, linear programming, economic production models, soft computing, fuzzy logic modeling, statistical bootstrapping, and combinations of two or more of these models. The perhaps most common estimation methods today are the parametric estimation models COCOMO, SEER-SEM and SLIM. They have their basis in estimation research conducted in the 1970s and 1980s and are since then updated with new calibration data, with the last major release being COCOMO II in the year 2000. The estimation approaches based on functionality-based size measures, e.g., function points, is also based on research conducted in the 1970s and 1980s, but are re-calibrated with modified size measures and different counting approaches, such as the use case points ^{[10]} or object points in the 1990s.
There are many ways of categorizing estimation approaches, see for example.^{[11]}^{[12]} The top level categories are the following:
Below are examples of estimation approaches within each category.
Estimation approach | Category | Examples of support of implementation of estimation approach |
---|---|---|
Analogy-based estimation | Formal estimation model | ANGEL, Weighted Micro Function Points |
WBS-based (bottom up) estimation | Expert estimation | Project management software, company specific activity templates |
Parametric models | Formal estimation model | COCOMO, SLIM, SEER-SEM, TruePlanning for Software |
Size-based estimation models^{[14]} | Formal estimation model | Function Point Analysis,^{[15]} Use Case Analysis, Use Case Points, SSU (Software Size Unit), Story points-based estimation in Agile software development, Object Points |
Group estimation | Expert estimation | Planning poker, Wideband delphi |
Mechanical combination | Combination-based estimation | Average of an analogy-based and a Work breakdown structure-based effort estimate^{[16]} |
Judgmental combination | Combination-based estimation | Expert judgment based on estimates from a parametric model and group estimation |
The evidence on differences in estimation accuracy of different estimation approaches and models suggest that there is no "best approach" and that the relative accuracy of one approach or model in comparison to another depends strongly on the context .^{[17]} This implies that different organizations benefit from different estimation approaches. Findings^{[18]} that may support the selection of estimation approach based on the expected accuracy of an approach include:
The most robust finding, in many forecasting domains, is that combination of estimates from independent sources, preferable applying different approaches, will on average improve the estimation accuracy.^{[18]}^{[19]}^{[20]}
It is important to be aware of the limitations of each traditional approach to measuring software development productivity.^{[21]}
In addition, other factors such as ease of understanding and communicating the results of an approach, ease of use of an approach, and cost of introduction of an approach should be considered in a selection process.
The most common measure of the average estimation accuracy is the MMRE (Mean Magnitude of Relative Error), where the MRE of each estimate is defined as:
MRE =
This measure has been criticized ^{[22]} ^{[23]} ^{[24]} and there are several alternative measures, such as more symmetric measures ^{[25]} , Weighted Mean of Quartiles of relative errors (WMQ) ^{[26]} and Mean Variation from Estimate (MVFE).^{[27]}
MRE is not reliable if the individual items are skewed. PRED(25) is preferred as a measure of estimation accuracy. PRED(25) measures the percentage of predicted values that are within 25 percent of the actual value.
A high estimation error cannot automatically be interpreted as an indicator of low estimation ability. Alternative, competing or complementing, reasons include low cost control of project, high complexity of development work, and more delivered functionality than originally estimated. A framework for improved use and interpretation of estimation error measurement is included in.^{[28]}
There are many psychological factors potentially explaining the strong tendency towards over-optimistic effort estimates that need to be dealt with to increase accuracy of effort estimates. These factors are essential even when using formal estimation models, because much of the input to these models is judgment-based. Factors that have been demonstrated to be important are: Wishful thinking, anchoring, planning fallacy and cognitive dissonance. A discussion on these and other factors can be found in work by Jørgensen and Grimstad.^{[29]}
The chronic underestimation of development effort has led to the coinage and popularity of numerous humorous adages, such as ironically referring to a task as a "small matter of programming" (when much effort is likely required), and citing laws about underestimation:
The first 90 percent of the code accounts for the first 90 percent of the development time. The remaining 10 percent of the code accounts for the other 90 percent of the development time.^{[30]}
-- Tom Cargill, Bell Labs
Hofstadter's Law: It always takes longer than you expect, even when you take into account Hofstadter's Law.
What one programmer can do in one month, two programmers can do in two months.
-- Fred Brooks
Adding to the fact that estimating development efforts is hard, it's worth stating that assigning more resources doesn't always help.
Software | Schedule estimate | Cost estimate | Cost Models | Input | Report Output Format | Supported Programming Languages | Platforms | Cost | License |
---|---|---|---|---|---|---|---|---|---|
AFCAA REVIC^{[32]} | Yes | Yes | REVIC | KLOC, Scale Factors, Cost Drivers | proprietary, Text | any | DOS | Free | Proprietary Free for public distribution |
Seer for Software^{[33]} | Yes | Yes | SEER-SEM | SLOC, Function points, use cases, bottoms-up, object, features | proprietary, Excel, Microsoft Project, IBM Rational, Oracle Crystal Ball | any | Windows, Any (Web-based)^{[34]} | Commercial | Proprietary |
SLIM^{[35]} | Yes | Yes | SLIM | Size (SLOC, Function points, Use Cases, etc.), constraints (size, duration, effort, staff), scale factors, historical projects, historical trends | proprietary, Excel, Microsoft Project, Microsoft PowerPoint, IBM Rational, text, HTML | any | Windows, Any (Web-based)^{[36]} | Commercial | Proprietary |
TruePlanning^{[37]} | Yes | Yes | PRICE | Components, Structures, Activities, Cost drivers, Processes, Functional Software Size (Source Lines of Code (SLOC), Function Points, Use Case Conversion Points (UCCP), Predictive Object Points (POPs) etc.) | Excel, CAD | any | Windows | Commercial | Proprietary |
|isbn=
value: length (help).CS1 maint: Multiple names: authors list (link)
|format=
requires |url=
(help). 28 (9): 896-901. doi:10.1145/4284.315122. ISSN 0001-0782.
Manage research, learning and skills at IT1me. Create an account using LinkedIn to manage and organize your IT knowledge. IT1me works like a shopping cart for information -- helping you to save, discuss and share.