Comment by Ghazouane on "How should developers go about estimating deadline for projects or features?"

Deadlines are toxic. Deadlines are never respected (400 % error) Deadlines are like playing poker (no way to be sure, even with KK) Estimation should be considered as what they are: a fu** estimation, not a truth. If management need it :

ask why ?
Push yourself into the motivation.
1. As a developer, answer: I can't give you estimation that is solid. But, we can talk about a POC, and iterate on it.
2. Then measure how much time your team took to finalize the feature. Double it. Or even triple it.

Else, ask the deadline. Close the discussion. If the feature is ready before the deadline, good. If it's not, what can you do ?

The rules of thumb: never sell what is not ready to be sell.

Search Hashnode