Differences

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

--- what_are_the_characteristics_of_a_good_estimate [2018/06/05 08:17] – hpsamios
+++ what_are_the_characteristics_of_a_good_estimate [2020/11/02 10:50] (current) – Cleaned up quote hans
@@ Line 4: / Line 4: @@
   * The estimates consistently reflect the capacity of the Team to deliver.
-  * The estimates consistently reflect the size of the work no matter what kind of work it is. For example, it should not matter that we are estimating a new feature or defects
+  * The estimates consistently reflect the size of the work no matter what kind of work it is. For example, it should not matter that we are estimating a new feature or defects.
-  * They are truly relative in that on a Team by Team basis an 8 is an 8 and an 8 is about 4 times a 2 no matter the source.
+  * They are truly relative in that, on a Team by Team basis, an 8 is an 8, and an 8 is about 4 times a 2 no matter the source.
-  * We provide data that allows the use of ranges of estimates to help understand the risk profile of the work. For example, at the release level, the Product Owner should be able to use best, average and worst velocities to understand what is likely to happen.
+  * Estimation data allows the use of ranges of estimates to help understand the risk profile of the work. A simple example of this is when the Product Owner uses best, average and worst velocities to understand what is likely to happen with their plan.
-{{tag>Team Estimates Forecast FAQ Points EstimationApproach}}
+It is worth saying again:
+>The estimates consistently reflect the capacity of the Team to deliver.
+They must be based on reality.
+{{tag>Team Estimates Forecast FAQ Points EstimationApproach}}