Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I appreciate the planning fallacy. I usually do this implicitly but I just changed an expected timeline on a JIRA epic from 80 hours to 160 days after reading this.


Watch out - there is a reverse bias, Parkinson's law, that work expands so as to fill the time available for its completion. This is why Elon Musk sets absurd deadlines he rarely can meet, to resist the expansion of make-work and administrative bloat which consumes longer-timed tasks.


Work behaves like a gas: It fills all the available space (time) and the smaller the space the more pressure you get.


There's a reason I encourage calling a collection of epics a "fantasy".


"I can look through all of my emails before the end of the day"


80 hours to 160 days? Or do you mean 80 hours to 160 hours?


The article said, “upgrade the units and double the estimate.”

So 20 hours -> 40 days -> 80 weeks -> 160 months


so 1 month -> 2 years but 4 weeks -> only 8 months


I think the proposed method should be categorized as a hyperbole.


30 days is 720 hrs -> 1440 days which is 3.9 years.

I love it




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: