Don't (guess)timate your projects, forecast with confidence
“The problem with spending a lot of time on estimating is that it can feel useful, but often is so inaccurate that it hardly yields much value to the business.” The best we can do is measure and forecast.
- from
- Engineering Team Management
- added
- 2026-10-10
- likes
- 0
similar
-
Dear Startup: You have no idea how much that costs kyleprifogle.com
“We are completely clueless about how long things should take.” Here is a trick to handle expectation of unreasonable estimates.
-
Why software projects take longer than you think: a statistical model erikbern.com
“Confirms the hunch that developers estimate the median well, but the mean ends up being much higher.”
-
Robert "Uncle Bob" Martin talk about professionalism in software development youtube.com
The only honest estimate is "I don't know". But you can come up with some kind of probability assessment, that will inform about the shape of the risk. This is not unlike PERT, where an activity is bounded by optimistic, pessimistic and most-likely time. Now if managers don't…
-
Developers spend most of their time figuring the system out lepiter.io
“A hand drawn picture about the current system is a belief. Decisions should never be based on beliefs. Not in engineering. (…) As software is highly contextual we cannot predict specific problems. We can only predict classes of problems.” And that's why it is hard to estimate…
-
When will the Agile Project be done? failfastmoveon.blogspot.com
How to make an educated forecast of the project's end date, based on the team's velocity.
-
Strategies for long Projects benbrostoff.github.io
Relentless, irrational optimism; Daily progress documentation; Compounding investments; Time budgeting.
Engineering Team Management › Project Management > Estimations: ““The problem with spending a lot of time on estimating is that it can feel useful, but often is so inaccurate that it hardly yields much value to the business.” The best we can do is measure and forecast.”