We recognize the difference between accurate estimates and precise estimates

Take our quick 9-question Free Assessment. Compare yourself against the practices of winning software organizations and discover your need level.

  • when we are asked to provide an estimate, we determine whether we’re supposed to be estimating or figuring out how to hit a target
  • when we are asked to provide an estimate, we determine whether we’re supposed to be estimating or figuring out how to hit a target
  • when we present an estimate, the merits of the process used to create the estimate and the resulting estimate are frequently debated
  • We are frequently pressured to provide precise estimates very early in the projects. Frequently these estimates are given off-the-cuff.
  • we create both “best case” and “worst case” estimates to encourage thinking about the full range of possible project outcomes
  • we always capture the results of our projects and use those results as the basis for our future estimates
  • We recognize that a good estimation process will highlight the risks resulting project will face
  • We use multiple techniques and look for convergence or spread amongst the estimates.
  • we have the developers who will do the actual work estimate the work tasks they are going to undertake