3 ms·
> 80% of the impact comes from 20% of the work. This simply has no basis in reality nor research and it pains me to see it propagated. The old VLSI design koa
by bsder 9y ago
> 80% of the impact comes from 20% of the work.
This simply has no basis in reality nor research and it pains me to see it propagated.
The old VLSI design koan is: "The first 90% of the project takes 90% of the schedule. The last 10% of the project also takes 90% of the schedule. 90% of the engineering occurs in the last 10% of the project."
- joshuamorton 9y agoYes it does. The 80/20 rule cleanly fits an exponential distribution. The assumption is then that the work to implement any given feature in a project follows an exponential , and this appears to hold reasonably true in practice.
- bsder 9y agoAll you did was move the question--why does this thing fit an exponential distribution? The birth project of agile--the Chrysler Comprehensive Compensation project--should have been a wonderful example of the 80/20 rule. They implemented the most important chunks of the project and got about 80% of the cases correct--totally awesome. Except--it wasn't. The value of the project was in handling all of the exceptional cases. And those cases started consuming VAST quantities of resource. 80/20 only works when you can interchangeably wipe out tasks without affecting the result. Most engineering is NOT like that. Analyzing the soil may not take very long when building a bridge, but you can't skip it.
- joshuamorton 9y agoAs far as I can see, what you described perfectly fits the 80/20 rule.
- noway421 9y agoThe exact proportion might differ and never is that, but the concept is conserved.
- valuearb 9y agohttp://www.crn.com/news/security/18821726/microsofts-ceo-80-20-rule-applies-to-bugs-not-just-features.htm http://www.crn.com/news/security/18821726/microsofts-ceo-80-... "About 20 percent of the bugs causes 80 percent of all errors, and--this is stunning to me--1 percent of bugs caused half of all errors."
- daxfohl 9y agoI was going to say the same thing. The 80 20 thing should be reserved to the higher-ups and marketers deciding what to implement. At the development level, zero value is provided by any less than 100 percent of the work. Too many developers just focus on the 20 percent, leaving the project 4/5 unfinished.
- gonzo41 9y agoYour assuming complete and correct requirements. 80 20 is great when you get fuzzy reqs and have to make a decision.