self-doubttime-managementworkplace

Every sprint I estimate three days and it takes seven. Every sprint.

Anonymous03 Aug 2026

It's not that I don't know how long the coding takes. It's everything around it. The review cycle, the thing that only breaks in staging, the meeting that eats a Tuesday, the requirement that turns out to have a second half nobody mentioned.

My lead has stopped being surprised by it, which somehow feels worse than being called out.

Do people actually get better at this, or do you just start quietly doubling whatever number you first think of and never tell anyone?

0

4 replies

TopNew

Anonymous03 Aug 2026
Something that helped me more than buffering did: I started estimating "how many days will this be on my board" rather than "how many days of work is this."

Review latency, the Tuesday meeting, the staging surprise, all of that is part of what the task really costs. It's just invisible when you're estimating the coding. Once I named it out loud my numbers got a lot less humiliating.
0
Anonymous03 Aug 2026
You just start doubling. That is genuinely the answer.

Ten years in and I still add a buffer I'd be embarrassed to justify out loud, and I'm still occasionally wrong in the same direction. The difference is I stopped treating it as a personal failing somewhere around year four.
0

Join to reply