User Tools

Site Tools


how_should_we_update_our_estimates

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
how_should_we_update_our_estimates [2019/07/01 13:31] hpsamioshow_should_we_update_our_estimates [2022/08/15 12:28] (current) hans
Line 7: Line 7:
 This is a mistake.  This is a mistake. 
  
-The reality is that no amount of additional planning would have resulted in a better estimate. In fact the evidence indicates otherwise; estimates get worse the more time you spend on it (mainly because you are building guesses on top of guesses as you think longer about the problem). It is simply wrong to "blame" the estimate for the fact that there is now more work than expected. The only way you could have found this out was by doing the work, getting the feedback from the customers. (See [[blog:our_estimates_are_terrible|Our Estimates are Terrible!]] for an example of this kind of thinking)+The reality is that no amount of additional planning would have resulted in a better estimate. In fact the evidence indicates otherwise; estimates get worse the more time you spend on it (mainly because you are building guesses on top of guesses as you think longer about the problem). It is simply wrong to "blame" the estimate for the fact that there is now more work than expected. The only way you could have found this out was by doing the work, getting the feedback from the customers. (See [[our_estimates_are_terrible|Our Estimates are Terrible!]] for an example of this kind of thinking)
  
 What this tells you is that you should not update a record of the estimate once you have started real work on it. That way an estimate stays an estimate, and has the same basis (and is good as) as any other estimate that we have in the system. Using this basis we can compare all the estimates, safe in the knowledge that they have the same status - "we haven't start working on this yet". What this tells you is that you should not update a record of the estimate once you have started real work on it. That way an estimate stays an estimate, and has the same basis (and is good as) as any other estimate that we have in the system. Using this basis we can compare all the estimates, safe in the knowledge that they have the same status - "we haven't start working on this yet".
Line 22: Line 22:
 All these things might necessitate an update to the Story estimate.  All these things might necessitate an update to the Story estimate. 
  
-Now the Team starts working the Story. Perhaps they committed to it during (Iteration) Planning. The Team is decomposing the work, determining who does what etc. At this point you should not update the "estimate" for this Story any more. As you complete the work, you might update the "actual" field. +Now the Team starts working the Story. Perhaps they committed to it during Iteration (Sprint) Planning. The Team is decomposing the work, determining who does what etc. At this point you should not update the "estimate" for this Story any more. As you complete the work, you might update the "actual" field. 
  
 This kind of thinking applies the higher level structures (Epics / Features) as well.  This kind of thinking applies the higher level structures (Epics / Features) as well. 
Line 30: Line 30:
 ====== Want To Know More? ====== ====== Want To Know More? ======
  
-  * [[blog:our_estimates_are_terrible|Our Estimates are Terrible!]]+  * [[our_estimates_are_terrible|Our Estimates are Terrible!]]
  
 {{tag>Team Estimates Forecast FAQ Points StoryPoints FeaturePoints}} {{tag>Team Estimates Forecast FAQ Points StoryPoints FeaturePoints}}
/home/hpsamios/hanssamios.com/dokuwiki/data/attic/how_should_we_update_our_estimates.1562013082.txt.gz · Last modified: 2020/06/02 14:28 (external edit)