Abstract
It is a human thing to err. Yet, we should learn from mistakes in order not to repeat them. At best, when we learn from others’ mistakes, we do not have to bear their consequences; others already did it.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
Scott M. Paton, “Four Days with W. Edwards Deming”, The W. Edwards Deming Institute, available at http://deming.org/index.cfm?content=653.
- 2.
- 3.
Web article “Estimation Games” published by Thomsett International. Last visited in June 2010. http://www.thomsettinternational.com/main/articles/hot/games.htm.
References
Lohr S (2007) Slow down, brawe multitasker, and don’t read this in traffic. New York Times, 25 March 2007
Averill-Snell J (2007) Is multi-tasking counterproductive? White Paper, Institute for Corporate Productivity
Meyer DE (2001) Multitasking has problems, study finds. CNN Tonight, 5 August, Sunday Transcript # 080502CN.V70, CNN
Rubinstein JS, Meyer DE, Evans JE (2001) Executive control of cognitive processes in task switching. J Exp Psychol Hum Percept Perform 27(4):763–797
Cohn M (2006) Agile estimating and planning. Prentice-Hall, Upper Saddle River, NJ
Dysert L, Eliott BG (2002) The estimate review and validation process. Cost Eng 44(1):17–22
Basili VR, Caldiera G, Rombach HD (1994b) The goal question metric approach. In: Marciniak JJ (ed) Encyclopedia of software engineering, vol 1, 2nd edn. Wiley, New York, pp 528–532
Betts M (2003) Why IT projects fail. Computerworld 37(34):44
GAO (2009) GAO cost estimating and assessment guide. best practices for developing and managing capital program costs. Report GAO-09-3SP, United States Government Accountability Office, Washington, DC
Glass RL (2002) Facts and fallacies of software engineering. Addison-Wesley Professional, Boston, MA
Jørgensen M (2009) How to avoid selecting bids based on overoptimistic cost estimates. IEEE Softw 26(3):79–84
Jørgensen M, Grimstad S (2005) Over-optimism in software development projects: ‘the winner’s curse. In: Proceedings of the 15th international conference on electronics, communications and computers, Puebla, Mexico, 28 February–2 March, pp 280–285
Jørgensen M, Grimstad S (2008) Avoiding irrelevant and misleading information when estimating development effort. IEEE Softw 25(3):78–83
Jørgensen M, Grimstad S (2010) Software development effort estimation: demystifying and improving expert estimation. In: Tveito A, Bruaset AM, Lysne O (eds) Simula research laboratory by thinking constantly about it. Springer, Berlin, pp 381–403
Jørgensen M, Grimstad S (2011) The impact of irrelevant and misleading information on software development effort estimates: a randomized controlled field experiment. IEEE Trans Softw Eng 37(5):695–707
Jørgensen M, Boehm B, Rifkin S (2009) Software development effort estimation: formal models or expert judgment? IEEE Softw 26(2):14–19
Mendes E, Mosley N (2008) Bayesian network models for web effort prediction: a comparative study. IEEE Trans Softw Eng 34(6):723–737
Morgenshtern O, Raz T, Dvir D (2007) Factors affecting duration and effort estimation errors in software development projects. Inform Softw Technol 49(8):827–837
PMI (2006) Practice standard for work breakdown structures, 2nd edn. Project Management Institute, Newtown Square, PA
PMI (2013) A guide to the project management body of knowledge (PMBOK Guide), 5th edn. Project Management Institute, Newtown Square, PA
Tversky A, Kahneman D (1974) Judgment under uncertainty: heuristics and biases. Science 185(4157):1124–1131
Yourdon E (2003) Death March. 2nd edn. Prentice-Hall
Jørgensen M, Indahl U, Sjøberg D (2003) Software effort estimation by analogy and ‘regression toward the mean’. J Syst Softw 68(3):253–262
Verzuh E (2011) The fast forward MBA in project management, 4th edn. Wiley, Hoboken, NJ
Author information
Authors and Affiliations
Further Reading
Further Reading
-
K. El Emam and A. Koru (2008), “A Replicated Survey of IT Software Project Failures,” IEEE Software, vol. 25, no. 5, pp. 84–90.
This article provides an overview of the studies presenting the rates and common causes of software project failures.
-
C. T. Jones (2006), “Social and Technical Reasons for Software Project Failures,” Cross-Talk: The Journal of Defense Software Engineering, vol. 19, no. 6, pp. 4–9.
This article discusses the most common causes of failures in software development projects. Two of them are failed estimates and project changes as sources of failed projects. Author goes deeper and analyzes the detailed root causes of the reasons of failed projects.
-
J. S. Armstrong (2001), Principles of forecasting: A handbook for researchers and practitioners. Kluwer Academic Publishers, Dordrecht, The Netherlands.
In Chap. 20 of his book, author specifies 139 principles of forecasting. He groups them into 16 categories including formulating forecasting problems, collecting necessary information, implementing forecasting methods, evaluating these methods, using these methods for prediction, and utilizing the predictions these methods deliver. For each practice, the author provides its description and specifies its purpose, conditions, as well as the strength and source of evidence behind the practice.
-
M. Jørgensen and K. Moløkken-Østvold (2003), “A Preliminary Checklist for Software Cost Management,” in Proceedings of the 3rd International Conference on Quality Software, p. 134.
This paper presents a checklist of best-practice software effort estimation activities. The checklist is a synthesis of experiences gained by multiple software estimation experts, including the authors of the paper. The checklist is structured according to 12 basic effort estimation activities, grouped into 4 major phases of project estimation: preparing for estimation, estimating, applying estimates, and learning from estimation feedback.
-
Wikipedia: List of cognitive biases
This Wikipedia page briefly lists cognitive biases considered in psychology. It is worth reading and considering which of them can affect the estimation approach we use and how to avoid them.
Rights and permissions
Copyright information
© 2014 Springer International Publishing Switzerland
About this chapter
Cite this chapter
Trendowicz, A., Jeffery, R. (2014). Effort Estimation Best Practices. In: Software Project Effort Estimation. Springer, Cham. https://doi.org/10.1007/978-3-319-03629-8_17
Download citation
DOI: https://doi.org/10.1007/978-3-319-03629-8_17
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-03628-1
Online ISBN: 978-3-319-03629-8
eBook Packages: Computer ScienceComputer Science (R0)