Differences

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

--- what_are_the_characteristics_of_a_good_estimate [2016/06/16 08:20] – hpsamios
+++ what_are_the_characteristics_of_a_good_estimate [2020/11/02 10:50] (current) – Cleaned up quote hans
@@ Line 3: / Line 3: @@
 Estimates need to reflect reality. Some basic characteristics of what we need from estimates include:
-  * The estimates consistently reflect the capacity of the team to deliver.
+  * 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. It should not matter that we are estimating a new feature or defects, that we are estimating for a production sprint or a release sprint.
+  * 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.
-  * 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.
-~~LINKBACK~~
+It is worth saying again:
-~~DISCUSSION~~
-{{tag>Team Estimates Forecast FAQ Points EstimationApproach}}
+>The estimates consistently reflect the capacity of the Team to deliver.
+They must be based on reality.
+{{tag>Team Estimates Forecast FAQ Points EstimationApproach}}