Read much more about that within my estimation book or watch my short video on Estimations, Targets, and Obligations.
3. Many comments for #NoEstimates demonstrate deficiencies in fundamental software estimation understanding.
I do not expect most #NoEstimates advocates to accept this thesis, but as somebody who does know a great deal about estimation I believe it’s obvious on its face. Here are a few good examples
(a) Are estimation and forecasting exactly the same factor? So far as software development company estimation is worried, yes they’re. (Just perform a Google or Bing search of “definition of forecast”.) Estimation, forecasting, conjecture–it’s the same fundamental activity, so far as software estimation is worried.
(b) Is showing someone several images of kitchen remodels which have been completed for $30,000 and implying the next kitchen redesign could be completed for $30,000 estimation? Yes, it’s. That’s an implementation of the technique known as Reference Class Forecasting.
(c) Does a couple of iterations, calculating team velocity, after which by using their empirical velocity data to project a completion date count as estimation? Yes it will. It’s not only estimation, it’s a really effective type of estimation. Software development company heard people reason that because velocity is empirically based, it’s not estimation. Good estimation is empirically based, to ensure that argument exposes deficiencies in fundamental knowledge of the character of estimation.
(d) Is counting the amount of tales carried out each sprint instead of story points, calculating the typical quantity of tales completed each sprint, and taking advantage of that for sprint planning, estimation? Yes, for the similar reasons indexed by point (c).(e) The majority of the #NoEstimates approaches which have been suggested, including (c) and (d) above, are approaches which were defined in my opinion Software Estimation: Demystifying the Black Art, printed in the year 2006. The truth that people individuals are declaring these lengthy-ago-printed techniques as “new” underneath the umbrella of #NoEstimates is yet another reason I only say most of the #NoEstimates comments demonstrate deficiencies in fundamental software estimation understanding.