#NoEstimates for the perplexed – a simple principle that makes estimations obsolete

When we think of estimation, we immediately associate some concepts that are attached to the estimation activity: listing all the work, sequencing all the work, assigning all the work, etc.  All of those activities are accessories to estimation. The fact is that a task does not have an intrinsic duration, it has a duration that …

A detailed comment on the practice of estimation in Software Development – a #NoEstimates post

OK, so a friend (who shall remain anonymous) sent me a message with some very good points bout estimation. This blog post explores those statements. It will be long, and detailed. Grab a cup of coffee, sit down and let’s do this! The first thing I’d like to comment on is the statement My start …

Accidental complication: another reason why estimates don’t work

Accidental complication Another reason why estimations can’t work goes by the name of accidental complication. J.B. Rainsberger introduced this concept at Oredev 2013 . The gist of the argument is this: every feature or functionality added to an existing project has two cost elements (what you want to estimate): Essential complication or g(e): How hard …