I'm glad @fulhack wrote this clear analysis about estimating software projects. It maybe needs another explanation about why the mean and median completion time for software development tasks are so different, so here's my take. (1/4)https://twitter.com/fulhack/status/1117968632536010754 …
-
-
So 10% of the project original schedule will take 90% of the actual time, there is some old joke about that
-
Yes. You can pick your n% and (100 - n)% as necessary.
End of conversation
New conversation -
-
-
No different than my experience in (big, many $$ millions) construction projects. I would have to estimate schedules/costs/materials with little data/requirements then do it. There is a rich literature on time/cost overruns in complex projects and software is no snowflake here
-
But construction projects don't have the feature that the majority of the perceived work is basically free, as it often is in software. Even the very worst overrun construction projects, like Berlin-Brandenburg Airport, aren't more that 5x over schedule...
- Show replies
New conversation -
-
-
one of my teachers was presenting things like that: the role of information technology is to automate things. So either the thing was already automated, and you can estimate but don't need to. Or it neither was, and you don't have the least idea of why and how much it will take
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I wrote a recent article on just thishttps://www.swiftcase.co.uk/blog/article/why-your-estimates-are-a-disaster-and-how-to-do-it-right …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.