Principles of Effort and Cost Estimation

One of the reasons for failed estimates is an insufficient background of estimators in the area of software estimation. Arbitrary selection and the blind usage of estimation methods and tools often lead to disappointing outcomes, while the underlying reasons remain unclear. In discussions with corporate management, it is not uncommon to hear the phrase “think of a number and multiply by three.” Deliberate decisions regarding the particular estimation method and its knowledgeable use require insight into the principles of effort estimation.

[1]  Cmmi Product Team.  CMMI for Development, Version 1.2 , 2010 .

[2]  Richard Stutzke.  Estimating Software-Intensive Systems: Projects, Products, and Processes (Sei Series in Software Engineering) , 2005 .

[3]  Capers Jones.  Social and Technical Reasons for Software Project Failures , 2006 .

[4]  Magne Jørgensen,et al.  Impact of effort estimates on software project work , 2001, Inf. Softw. Technol..

[5]  A. Salas.  Cost estimation: more than an analytical tool , 2004, 2004 IEEE Aerospace Conference Proceedings (IEEE Cat. No.04TH8720).

[6]  Kenneth S. Rubin,et al.  Essential Scrum: A Practical Guide to the Most Popular Agile Process , 2012 .

[7]  Barbara A. Kitchenham,et al.  Modeling Software Bidding Risks , 2003, IEEE Trans. Software Eng..

[8]  Michael A. Ross,et al.  Next Generation Software Estimating Framework: 25 Years and Thousands of Projects Later , 2008 .

[9]  Magne Jørgensen.  Top-down and bottom-up expert estimation of software development effort , 2004, Inf. Softw. Technol..

[10]  Dag I. K. Sjøberg,et al.  The impact of customer expectation on software development effort estimates , 2004 .

[11]  June M. Verner,et al.  Why did your project fail? , 2009, Commun. ACM.

[12]  Barbara A. Kitchenham,et al.  A framework for evaluating a software bidding model , 2005, Inf. Softw. Technol..

[13]  Khaled El Emam,et al.  A Replicated Survey of IT Software Project Failures , 2008, IEEE Software.

[14]  Phillip G. Armour.  The inaccurate conception , 2008, CACM.

[15]  Edward Yourdon,et al.  Death March , 1997 .

[16]  Phillip G. Armour.  To plan, two plans , 2005, CACM.

[17]  Peter V. Norden.  Curve Fitting for a Model of Applied Research and Development Scheduling , 1958, IBM J. Res. Dev..

[18]  Yingxu Wang,et al.  Software Engineering Foundations: A Software Science Perspective , 2007 .

[19]  James J. Jiang,et al.  The effects of change control and management review on software flexibility and project performance , 2008, Inf. Manag..

[20]  F. N. Parr,et al.  An Alternative to the Rayleigh Curve Model for Software Development Effort , 1980, IEEE Transactions on Software Engineering.

[21]  Yingxu Wang,et al.  On Laws of Work Organization in Human Cooperation , 2007, Int. J. Cogn. Informatics Nat. Intell..

[22]  Frederick P. Brooks,et al.  The Mythical Man-Month: Essays on Softw , 1978 .

[23]  Phillip G. Armour.  The unconscious art of software testing , 2005, CACM.

[24]  R.N. Charette,et al.  Why software fails [software failure] , 2005, IEEE Spectrum.

[25]  Suku Nair,et al.  A Model for Software Development Effort and Cost Estimation , 1997, IEEE Trans. Software Eng..

[26]  Barry Boehm,et al.  Top 10 list [software development] , 2001 .

[27]  Anette C. Lien,et al.  A survey on software estimation in the Norwegian industry , 2004 .