Skip to Content

Changes for page Effort Estimation

Last modified by chrisby on 2023/12/07 22:12
From version 1.9
edited by chrisby
on 2023/10/12 13:59
Change comment: There is no comment for this version
To version 1.10
edited by chrisby
on 2023/10/21 14:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -8,5 +8,5 @@
8 8  * **The Golden Story**: At the very beginning of a project, choose a medium effort story to be the "golden story". It acts as a standard against which every other story must be compared and its estimated effort questioned. This prevents the estimated story points from being artificially inflated later in the project, e.g. due to pressure from management to increase the team's velocity. Velocity is a metric, not a goal, and should be approximately constant throughout the project.
9 9  * **Cheap Estimates**: Breaking down a task and estimating the subtasks gives a higher accuracy than estimating the original task. Theoretically, this breakdown can be repeated until code level is reached and the feature is implemented, but this would no longer be a planning process. Planning should be cheap, estimating should take little time and be as accurate as necessary.
10 10  * **Increasing Estimate Precision**: Initial estimates are highly inaccurate. As the project progresses, new insights and feedback loops allow the accuracy to be increased.
11 -* **Uncertainty & Honesty**: Honestly communicate the level of certainty for each of your estimate. Choose wisely between "I'm sure that ...", "I think ..." I guess ...". The most honest answer is sometimes "I don't know". Uncertain estimates can still be valuable and can be modeled by probabilities or ranges of estimates.
11 +* **Uncertainty & Honesty**: Be honest about the level of certainty you give for each of your estimates. Sometimes the most honest answer is "I don't know. Uncertain estimates can still be valuable and can be modeled by probabilities or ranges of estimates. An example is the Three-Point Estimation technique mentioned at the beginning of this article.
12 12  * **Absolute vs Relative Estimates**: Absolute estimates are best ("Task A is worth 3 points"), but relative estimates can still be valuable ("Task A will require twice as much effort as Task B").