Re:Cognitive Biases in Software Engineering
by pessimizer on Monday June 30, 2014 @11:42AM
(#7965607)
Sometimes, for business reasons, it's crucial that you pull a number out of your ass. My policy is to make that number as high as will be acceptable by management, and to refuse the project if that number is less than twice the length of my worst case scenario nightmare. Then, deliver early. Basically the same as the OP.
Are you advocating something different here?
Re:Cognitive Biases in Software Engineering
by chriswarbo on Monday June 30, 2014 @12:57PM
(#7966107)
That's known as the Scotty Principle, or Scotty Factor ;)
Re:Cognitive Biases in Software Engineering
by pessimizer on Tuesday July 01, 2014 @11:50AM
(#7971474)
Never heard that before! Just seems the optimal way to look like you know what you're doing:)
Re:Cognitive Biases in Software Engineering
by afarrell on Tuesday July 01, 2014 @07:24AM
(#7970080)
Well, I'm advocating finding a way to estimate things that doesn't involve pulling things out of your ass. Doing that has always felt a bit dishonest to me. Yet, I don't actually know any other method because I haven't finished the book.
What exactly is the point you are trying to make?
That isn't estimation. That is pulling a number out of your ass. Try something for me. For each of these data points, write down a low estimate and a high estimate that give you a 90% probability of being within that range.
Surface Temperature of the Sun: Low [___] -- High [__] Latitude of Shanghai: Low [___] -- High [__] Area of the Asian continent: Low [___] -- High [__] The year of Alexander the Great's birth: Low [___] -- High [__] Total value of U.S. currency in circulation in 2004: Low [___] -- High [__] Total volume of the Great Lakes: Low [___] -- High [__] Worldwide box office receipts for the movie Titanic: Low [___] -- High [__] Total length of the coastline of the Pacific Ocean: Low [___] -- High [__] Number of Book titles published in the US since 1776: Low [___] -- High [__] Heaviest blue whale ever recorded: Low [___] -- High [__]
Now, you might think this is a silly exercise because you don't have experience with the scale of these things, but how often do you estimate the time it takes you to build a product you aren't yet familiar with something using a tool you're not yet familiar with or people you aren't familiar with?
The answers are here: http://my.safaribooksonline.com/book/software-engineering-an...
(This quiz is taken from Software Estimation by Steve McConnel (Microsoft Press, 2006) and is copyright 2006 Steve McConnel. All rights Reserved. Permission to copy this quiz is granted provided that this copyright notice is included.)