Forecast, don't guesstimate your software projects
I appreciate new approaches to software estimation. But while this is an interesting approach, it fails to adequately address the primary issue: defining a &quot;unit of work&quot;.<p>If it were possible to predict, with any degree of confidence, that task A (to do) is approximately equal to, or a 1&#x2F;x fraction of, task B (completed), then the estimation problem would not be nearly so difficult to begin with.<p>Yet that&#x27;s what this approach requires.<p>So cool idea, but not terribly applicable to actual projects in my opinion, unless you&#x27;re able to break down projects into easily definable and predictable units of work (and yes, I know that there are various frameworks that attempt to do just that, with mixed results).