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

I find it challenging to estimate my own time in tasks. Part of every task is figuring out how to actually do the thing you are wanting to do, and sometimes that takes 5 minutes and sometimes much longer. So I am terrible at estimating my own time, and even worse at estimating someone else’s. It doesn’t add pressure to a person if you give them a time goal they know is basically arbitrary.


Software estimation is very hard.

This is what scrum (done well) helps with. Unless the software was horribly written, it’s usually easy to estimate effort for very modest, well-defined changes.

Take a large enhancement or overhaul, however, and estimates will be wildly off and it’s because of the iceberg effect of unknowns.

What scrum forces the inexperienced teams to do is start breaking down, plan and incrementally chip away at a ill-defined, large request by turning it into many smaller and better understood deliverables.

It’s what very good teams do, though they do it without the need for formality.


That means the task is underspecified. You should schedule a "figure this out" instead, and once the task is well defined it can be done.


You never know if you have really completed the "figure it out" task until the "get it done" task is completed.


A meeting to plan for the meeting. Instead of turtles, it's meetings all the way down.


I never said a meeting. That says a lot about you :p




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

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

Search: