Differences

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

--- how_do_we_use_story_point_estimates_to_forecast [2020/06/02 14:22] – external edit 127.0.0.1
+++ how_do_we_use_story_point_estimates_to_forecast [2020/11/02 10:54] (current) – readability hans
@@ Line 30: / Line 30: @@
 The Product Owner should leverage this information in their forecasts. A typical approach is to use three data points - the minimum, the average, and the maximum - to be more informed about the forecast. So here the minimum is 21 Points, the maximum is 30, and the average is around 24-25. We can use this information with our prioritized backlog:
-{{ :blog:screen-shot-2015-08-17-at-2.33.41-pm.png?nolink&600 |}}
+{{ screen-shot-2015-08-17-at-2.33.41-pm.png?nolink&600 |}}
 The way to think about this is to look at the items between the average and maximum Velocity - these have a significant risk of not happening based on current knowledge. If you see things there that are a significant problem, then these need to be worked now. Perhaps we need to re-prioritize the Backlog to bring in the items of concern. Perhaps we need to find another Team to do the work. Perhaps …
@@ Line 53: / Line 53: @@
 This thinking is really an example of:
-<WRAP Box> “what is the best use of our people’s time?"</WRAP>
+>“what is the best use of our people’s time?"
 In reality re-estimating the Features can be a lot of work and the end result is often "we need to finish the Features we have started." Most organizations end up saying that “we will treat Feature carry over work differently”. Let's say we have some uncompleted Features in the current PI, PI 1. Rather than re-estimating the Feature for work that is carried over, we will simple treat carry-over work as “top priority” and assume that it will be scheduled first. These become the top items on the list for PI 2. Then the only thing we do a WSJF on is “new” PI 2 stuff that is coming out of the Program Backlog.
@@ Line 80: / Line 81: @@
 ====== Want to Know More? ======
-  * [[blog:why_a_plan_based_on_average_velocity_will_fail|Why a Plan Based on Average Velocity Will Fail?]]
+  * [[why_a_plan_based_on_average_velocity_will_fail|Why a Plan Based on Average Velocity Will Fail?]]
-  * [[blog:why_should_we_work_harder_to_eliminate_the_effect_of_dependencies|Why Should We Work Harder to Eliminate the Effect of Dependencies?]]
+  * [[why_should_we_work_harder_to_eliminate_the_effect_of_dependencies|Why Should We Work Harder to Eliminate the Effect of Dependencies?]]
   * [[how_can_we_forecast_when_we_do_not_have_a_lot_of_data|How Can We Forecast When We Do Not Have a Lot of Data?]]
 {{tag>Team Estimates Forecast FAQ Points StoryPoints FeaturePoints}}