Differences

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

--- what_alternative_estimation_approaches_are_there [2019/01/09 14:43] – ↷ Links adapted because of a move operation hpsamios
+++ what_alternative_estimation_approaches_are_there [2020/06/10 12:53] (current) – ↷ Links adapted because of a move operation hans
@@ Line 5: / Line 5: @@
 Alternative approaches include:
-  * #noestimates approaches: there is a lot discussion about this thinking and the discussion is worthwhile. See [[blog:do_we_need_points_to_generate_a_release_burn-up_chart|Do We Need Points To Generate a Release Burn-up Chart?]] for this type of thinking.
+  * #noestimates approaches: there is a lot discussion about this thinking and the discussion is worthwhile. See [[do_we_need_points_to_generate_a_release_burn-up_chart|Do We Need Points To Generate a Release Burn-up Chart?]] for this type of thinking.
   * Cycle time and throughput: More generally, using cycle time and throughput information directly can help.
   * XP based: 0, 1, 2, 4, split. Used to help encourage smaller pieces of work.
-  * High / low estimates: The approaches generate a single number to estimate size of story as well as a velocity for the team, usually an average. When forecast the future we should be talking about a range of possible values rather than a single number as the future is not certain.
+  * High / low estimates: The approaches generate a single number to estimate size of a Story. When forecasting the future we should be talking about a range of possible values rather than a single number as the future is not certain.
-  * Probabilities: A more rigorous approach is to use actual probabilities to talk about what might happen. See [[blog:why_a_plan_based_on_average_velocity_will_fail|Why a Plan Based on Average Velocity Will Fail?]] for the thinking here.
+  * Probabilities: A more rigorous approach is to use actual probabilities to talk about what might happen. See [[why_a_plan_based_on_average_velocity_will_fail|Why a Plan Based on Average Velocity Will Fail?]] for the thinking here.
-  * Dependencies: Estimation approaches that directly factor a understanding of dependencies to drive better information. See [[blog:why_should_we_work_harder_to_eliminate_the_effect_of_dependencies|Why Should We Work Harder to Eliminate the Effect of Dependencies?]] for some thinking here.
+  * Dependencies: Estimation approaches that directly factor a understanding of dependencies to drive better information. See [[why_should_we_work_harder_to_eliminate_the_effect_of_dependencies|Why Should We Work Harder to Eliminate the Effect of Dependencies?]] for some thinking here.
-  * Expansion: Estimation approaches that also factor in expansion of scope, since in most cases scope increases, rather than decreases as the team implements and the customer sees what is possible.
+  * Expansion: Estimation approaches that also factor in expansion of scope, since in most cases scope increases rather than decreases, as the team implements and the customer sees what is possible.
   * Utilization / WIP: Understanding the impact of high utilization on estimates. See [[why_does_high_a_utilization_rate_make_it_impossible_to_create_good_estimates|Why Does a High Utilization Rate Make It Impossible to Create Good Estimates?]] for more information.