Solution: divide the project into fewer tasks :)
Solution: divide the project into fewer tasks :)
Prioritized (short) iterative development is the only path to success.
Apparently software engineers as a group seem to think "fuck you, it's done when we feel like it" is a valid answer?
I disagree, and have always offered estimates, probabilities and contingencies when talking to product owners when I was a lead. I tracked data, and adjusted accordingly, and ended up giving estimates that were statistically sound.
I don't necessarily expect individual contributors to do the same, but anyone that's a lead should be an adult and account for their team's actual productive capacity. This is absolutely expected of a building company, even if you don't expect a single dude with a hammer to be able to estimate how long the project will take.
If you are giving regularly accurate long-term estimates, I'd suggest that you create a consultancy that performs this service or teaches how to do it. Most companies and teams just aren't capable of doing this.
Please explain exactly what you mean by this.