The Community for Technology Leaders
RSS Icon
Subscribe
Issue No.03 - May/June (2008 vol.25)
pp: 78-83
Magne J?rgensen , Simula Research Laboratory
Stein Grimstad , Simula Research Laboratory
ABSTRACT
Software development effort estimates are reported to be highly inaccurate and systematically overly optimistic. Empirical evidence suggests that this problem is caused to some extent by the influence of irrelevant and misleading information—for example, information about the client's budget. The only effective way to eliminate this influence is to avoid exposure to such information. Other means, such formal effort estimation models, improved analysis of requirement specifications, and better selection of estimators, might have a positive effect but don't eliminate the influence. Proposed changes to the estimation process can help eliminate unnecessary information, leading to more realistic effort estimation.
INDEX TERMS
software development, effort estimation, estimation irrelevant information
CITATION
Magne J?rgensen, Stein Grimstad, "Avoiding Irrelevant and Misleading Information When Estimating Development Effort", IEEE Software, vol.25, no. 3, pp. 78-83, May/June 2008, doi:10.1109/MS.2008.57
REFERENCES
1. K. Moløkken and M. Jørgensen, "A Review of Software Surveys on Software Effort Estimation," Proc. Int'l Symp. Empirical Software Eng., IEEE CS Press, 2003, pp. 223–230.
2. S. Grimstad and M. Jørgensen, "Inconsistency in Expert Judgment Based Estimates of Software Development Effort," J. Systems and Software, vol. 80, no. 11, 2007, pp. 1770–1777.
3. R.M. Hogarth, Educating Intuition, Univ. of Chicago Press, 2001.
4. J.S. Edwards and T.T. Moores, "A Conflict between the Use of Estimating and Planning Tools in the Management of Information Systems," European J. Information Systems, vol. 3, no. 2, 1994, pp. 139–147.
5. D.J. Koehler and C.S.K. Poon, "Self-Predictions Overweight Strength of Current Intentions," J. Experimental Social Psychology, vol. 42, 2006, pp. 517–524.
6. B. Boehm et al., Software Cost Estimation with Cocomo II, Prentice-Hall, 2000.
7. C.R. Symons, Software Sizing and Estimating—Mk II FPA, John Wiley &Sons, 1991.
8. M. Jørgensen, "Forecasting Software Development Work Effort: Evidence on Expert Judgment and Formal Models," Int'l J. Forecasting, vol. 23, no. 3, 2007, pp. 449–462.
9. F.J. Heemstra and R.J. Kusters, "Function Point Analysis: Evaluation of a Software Cost Estimation Model," European J. Information Systems, vol. 1, no. 4, 1991, pp. 223–237.
10. M. Jørgensen, "An Empirical Evaluation of the MkII FPA Estimation Model," Proc. Norwegian Informatics Conf., 1997, pp. 7–18.
11. J.S. Edwards and T.T. Moores, "A Conflict between the Use of Estimating and Planning Tools in the Management of Information Systems," European J. Information Systems, vol. 3, no. 2, 1994, pp. 139–147.
12. M. Jørgensen and S. Grimstad, "Over-optimism in Software Development Projects: 'The Winner's Curse,'" Proc. IEEE Conf. Electronics, Comm., and Computers (CONIELECOMP), IEEE CS Press, 2005, pp. 280–285.
23 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool