DEV Community

loading...

Discussion on: ⏰ How to nail time estimations

Collapse
pjotre86 profile image
pjotre86 • Edited

That's confusing! You really NEVER know how long you'd need for a task? You can't even tell if it's gonna be a one-liner or completely unknown?

The people asking for estimations are often not developers. That means they naturally have even less of an idea of how big a task is. So in most cases you should be able to give them at least a rough estimation. If not, then I agree, be honest and say it. But never knowing how much work something would be, that doesn't sound right.

Collapse
jonrandy profile image
Jon Randy • Edited

Of course I'm not saying I never know - I definitely know sometimes, but then that is not an estimation. By estimation I mean attempting to break a largely unknown task down and come up with a time or approximate time it might take. This is what I have found is ultimately futile and a waste of valuable time that could be spent just getting on with it

Thread Thread
carmenhchung profile image
Carmen Chung Author

Oh yeah - if you have no clue about the task/it's largely unknown, then estimating is often just plucking a random number out of the air, which is not helpful. We have R&D sessions every fortnight where we sit down and try to actually eliminate most major unknowns on upcoming tickets, to try to put us in a position where we can estimate more accurately. Sometimes it works...sometimes it doesn't (you can't always eliminate every unknown, even when doing prep).