Software estimation is hard – do it anyway
jacobian.org
Software estimation is hard – do it anyway
1–10 of 231 posts
Re: Software estimation is hard – do it anyway
#2Only if you work in an extremely repeatable well trodden domain. If you are so skilled at estimation, I’m sure Tesla would love you to tell them how long FSD will take and would pay a premium!
Re: Software estimation is hard – do it anyway
#3Re: Software estimation is hard – do it anyway
#4‘You can get good at estimation’ Only if you work in an extremely repeatable well trodden domain. If you are so skilled at estimation, I’m sure Tesla would love you to tell them how long FSD will take and would pay a premium!
Re: Software estimation is hard – do it anyway
#5‘You can get good at estimation’ Only if you work in an extremely repeatable well trodden domain. If you are so skilled at estimation, I’m sure Tesla would love you to tell them how long FSD will take and would pay a premium!
If you really do think that every project you're working on is completely incomparable to anything you've worked on before you're probably concentrating on too low level details.
Re: Software estimation is hard – do it anyway
#6‘You can get good at estimation’ Only if you work in an extremely repeatable well trodden domain. If you are so skilled at estimation, I’m sure Tesla would love you to tell them how long FSD will take and would pay a premium!
People love to conflate research with development out of "R&D", but the latter is a lot more predictable than the former. Repeatable, well trodden domains are 99,9% of development work out there.
Re: Software estimation is hard – do it anyway
#7Just keep breaking the problem down into sub units that you or your team understand and can fairly accurately understand the effort and risk of (because they've been done before)
Re: Software estimation is hard – do it anyway
#8Re: Software estimation is hard – do it anyway
#9If you can't avoid giving estimation, try to pad it as much as possible, add every single uncertainty to the task list, and estimate very conservative. Add enough time for testing, communication, work on change requests.
And even after the original estimate is approved / published be sure to communicate updates to the estimation after every single change request, question, bug, new insight.
And if something by chance take less time than estimated, make sure not to decrease estimation, but to use it as a buffer.