DEV Community

Discussion on: Why Estimates Are Waste

Collapse
 
maddy profile image
Maddy • Edited

I agree with many of the points you made.

To add on this:

  • Estimates are meant to give a prediction on the complexity of a task. Not how long it's going to take to complete the task. This is where, many times, my frustration has come from as a software engineer.

  • Just because a ticket is a 3-pointer, it still doesn't mean you'll complete it "faster".

  • Software engineering has often a level of unpredicatibility and unknown. And indeed, it's part of the job and your responsibility to Google/read/ask about what you don't know.

  • My interpretation of "I had done X before" means that I know 80% of the task. The remaining 20% needs to be figured out, and that 20% may or may not be easy to navigate.

  • Estimates are useful for management, because they want to know when they'll be able to release a money-making feature to customers. I find them pointless from the developer's point of view.

But, since software engineering is a lot about business, we have no other choice than caring about estimates and trying to give the best guess.