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 …
-
Show this thread
-
Unlike almost any other production task or industry, software development seeks solutions which are, at their most basic, repeatable; at best, highly abstract and general. One solution can be reused thousands or billions of times for almost zero cost. (2/4)
1 reply 1 retweet 5 likesShow this thread -
All the tasks which can be completed using known solutions, no matter how large they seem, will be competed quickly. So what's left after that? It might be a small part of the total, but it will need new solutions, working things out for the first time; all the unknowns. (3/4)
1 reply 1 retweet 5 likesShow this thread -
So that's where almost all the time is spent: tasks that you've never solved before. And how do you estimate them, when you have no data? It's at best a guess. (4/4)
4 replies 3 retweets 20 likesShow this thread -
Replying to @propensive
So 10% of the project original schedule will take 90% of the actual time, there is some old joke about that
1 reply 0 retweets 0 likes
Yes. You can pick your n% and (100 - n)% as necessary.
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.