Slashdot Mirror

← Back to Stories (view on slashdot.org)

Can Software Schedules Be Estimated?

Posted by timothy on from the now-stop-abusing-the-mozilla-team dept.

J.P.Lewis writes " Is programming like manufacturing, or like physics? We sometimes hear of enormous software projects that are canceled after running years behind schedule. On the other hand, there are software engineering methodologies (inspired by similar methodologies in manufacturing) that claim (or hint at) objective estimation of project complexity and development schedules. With objective schedule estimates, projects should never run late. Are these failed software projects not using proper software engineering, or is there a deeper problem?" Read on for one man's well-argued answer, which casts doubt on most software-delivery predictions, and hits on a few of the famous latecomers.

"A recent academic paper Large Limits to Software Estimation (ACM Software Engineering Notes, 26, no.4 2001) shows how software estimation can be interpreted in algorithmic (Kolmogorov) complexity terms. An algorithmic complexity variant of mathematical (Godel) incompleteness can then easily be interpreted as showing that all claims of purely objective estimation of project complexity, development time, and programmer productivity are incorrect. Software development is like physics: there is no objective way to know how long a program will take to develop."

Lewis also provides a link to this "introduction to incompleteness (a fun subject in itself) and other background material for the paper."

18 of 480 comments (clear)

  1. Software Schedules by JohnHegarty · · Score: 4, Funny

    There is only two type of software schedules

    1) As long as it takes.

    2) Take your best estimate , and double it and add 5 or something....

    It prefer the as long as it takes. Other wise you end up with something like Windows Me.

    --
    Cruise TT
    1. Re:Software Schedules by flegged · · Score: 2, Funny

      Software design is ultimate application of Hofstader's Law, which states:

      Everything takes longer than you expect, even when you take into account Hofstader's Law.

      --

      "I think he was truly surprised at how little I cared about how big a market the Mac had" - Linus on Jobs
    2. Re:Software Schedules by rodgerd · · Score: 3, Funny

      Most successful large projects are in COBOL, assembler, or REXX. Especially COBOL.

  2. Re:Double the number, add one and raise the unit! by dattaway · · Score: 4, Funny

    We can get it done by next week! We can do this because we have just #defined a day as having 2000 hours.

  3. Incompleteness by wetdogjp · · Score: 3, Funny

    Lewis also provides a link to this "introduction to incompleteness" (a fun subject in itself)

    I started writing a paper about this topic once, but I never finished it.

    -WetDog

    1. Re:Incompleteness by Anonymous Coward · · Score: 1, Funny

      I've been meaning to write a SegFault article about the Art of Procrastination, but I keep putting it off...

    2. Re:Incompleteness by Black+Parrot · · Score: 2, Funny


      > started writing a paper about this topic once, but I never finished it.

      Me t

      --
      Sheesh, evil *and* a jerk. -- Jade
  4. Actually.... by Anonymous Coward · · Score: 3, Funny

    ...the real reason estimating doesn't work is that there's no way to predict how much time programmers will spend reading Slashdot...

  5. Re:Of course they can be estimated. by john@iastate.edu · · Score: 5, Funny
    Writing software is not like building bridges because halfway through the project some dumbass from marketing doesn't come down and tell you that concrete is out and so it needs to be a steel bridge. Oh, and those tacky cables have got to go -- the focus group hated them.

    --
    Shut up, be happy. The conveniences you demanded are now mandatory. -- Jello Biafra
  6. Re:Slashdot readers are students? by dattaway · · Score: 3, Funny

    I thought most of us worked for the NSA and FBI.

  7. Re:It's all a bunch of bull.. by ogren · · Score: 2, Funny

    He very carefully laid out the algorithm - I don't have my textbook handy, but it involved elementary mathematical operations on estimated man hours, estimated lines of code, estimated overhead, etc., then at the end -- and I am not making this up -- they multiply the result by a "magic number".

    It hit me then that the whole discipline of estimating cost completion is all bullshit. You might as well be estimating with a crystal ball or divining the future with chicken bones. Since I've been working, the best advice I've gotten so far has been "take how long you think it'll take and double it".

    Back when I was in middle school my math teacher told me that in order to calculate the area of a circle you had to square the radius and (I am not making this up!) multiply it by a magic number. They even had some hocus-pocus name for the magic number.

    It was then that I new the entire field of mathematics had been invented by a bunch of wackos, and that my method was much better. I guess how large I think the area is and then double it. Works for me.

    All equations with constants are obviously flawed.

  8. Where did you hear such a thing? by Aceticon · · Score: 1, Funny
    It's totally untrue!!!

    We're all just normal geeks ...

    No need to worry about those sirenes ...

    It must be for your next door neighbour ...

    Just stay where you are ...

    There's nothing to worry about ...

  9. Re:Of course they can be estimated. by Anton+Anatopopov · · Score: 2, Funny
    Writing software is not like building bridges because halfway through the project some dumbass from marketing doesn't come down and tell you that concrete is out and so it needs to be a steel bridge. Oh, and those tacky cables have got to go -- the focus group hated them

    Oh yeah, and while we are at it, it is no longer a bridge we want, it is a tunnel. And it doesn't cross the river any more, it is going to be used as a large wine cellar. And the 50million dollar budget is now 2 million, the 3 year estimate is now six weeks, we need you to use baseball bats and plastic spoons to dig the damn thing, oh yeah and when will it be ready ?

  10. From the desk of BOFH by Anonymous Coward · · Score: 1, Funny
    Here's how a BOFH handles estimates:

    • It'll take as long as it takes -- and it'll take longer if you don't shut up and let me do my fucking job!
    • What?! You want me to predict the future too?! Hire a sorcerer and ask him how long this'll take!
    • It would have been done already if you kept your mouth shut!
  11. A good quote... by C_Mattie · · Score: 2, Funny

    "They didn't want it right, they wanted it Wednesday."

    --
    "If you're not failing every now and again, it's a sign you're not doing anything very innovative." -- Woody Allen
  12. Magic 8 Ball Estimations by staplin · · Score: 2, Funny

    One of my former coworkers had a relatively accurate method of predicting schedules using a Magic 8 Ball. For example:

    "Will this project be done in 8 weeks?"
    shake "Outlook not good"
    "OK, how about 12 weeks?"
    shake "Maybe"
    "Hmmm. Let's make it 15 to be sure..."
    shake "Yes"
    "Yep, this project will take 15 weeks."

    And it really annoys managers when they discover that you used a Magic 8 Ball, and then it confounds them when it is right...

  13. Standard estimate by sulli · · Score: 4, Funny

    "You tell me the month, I'll tell you the year"

    --

    sulli
    RTFJ.
  14. Deadline estimate by $criptah · · Score: 2, Funny

    Let's assume that it is possible to have a fixed deadline, then in order to meet it you will need to get all the specifications for the program, such that they will not be changed while you're developing it. Moreover you need to have a boss that doesn't add functionality to an already started project. All these things are completely impossible, that's why our initial assumption was
    incorrect. A very flexible deadline? Maybe...