> That estimate turned out to be wildly incorrect

> That estimate turned out to be wildly incorrect. The project ended up taking a year longer than I’d originally projected. The reasons are complex; the short version is that I made some major technical assumptions that turned out to be wildly incorrect. Several large architectural changes I’d thought we could avoid turned out to be unavoidable, adding all sorts of dependencies and additional work to the project. Honestly, I can't help but judge either the company or the author. What kind of project ends up taking more than a year to complete? Wait... it's "a year longer than I’d originally projected." So what was the original estimate? Six months? It doesn't matter how complex it was. If it is taking that long, the project should have been a smaller piece of what was planned. The author talks about re-estimating, communicating early, and owning up to your mistakes, which is all fine advice, but what if the project itself was too ambitious, and too broad to have a reasonable estimate?