Last week’s post about misunderestimations (part 1) considered the practical difficulty of estimating software effort. Uncertainty of estimates is created by complexity and the infamous, but poorly understood, “unknown unknowns”. The uncertainty is too often ignored. Consider the best way to estimate… Team Lead: I need to know precisely how long task X will take. […]![]()
