DEV Community

loading...

Discussion on: ⏰ How to nail time estimations

carmenhchung profile image
Carmen Chung Author

I agree spending time estimating can be annoying, and that badly-estimated deadlines are very often dangerous, and detrimental to code quality.

I think we'll need to agree to disagree on not doing estimates at all though. I think being a good team player means keeping the rest of the company informed of when they can expect a feature to launch. In my experience, partnerships needs to prepare workshops for partners (and customers, in my current situation), communications/marketing needs to get media releases ready, and management needs to inform investors/the Board about how their money is being spent. It's unfair on them to suddenly spring a feature launch and expect them to scramble to get their work done, especially if there's time-sensitivity to what they do (i.e. they need to get their media releases/workshops done within a week of the feature being launched).

But again, that's just my experience - if you don't have people relying on your time estimates, then by all means, estimates are pretty pointless!

Thread Thread
190245 profile image
Dave

Why the hell can I only click "love" once on your posts? You deserve a lot more than that!

Thread Thread
carmenhchung profile image
Carmen Chung Author

Thanks so much Dave, really appreciate it! Also love your "go back to the drawing board" comment - it's super important for people (not just devs) to raise when things aren't possible early on, and to encourage re-thinking the solution (and sometimes the problem, haha).