Differences

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

Link to this comparison view

Both sides previous revision Previous revision
blog:why_a_plan_based_on_average_velocity_will_fail [2016/07/03 13:43]
127.0.0.1 external edit
blog:why_a_plan_based_on_average_velocity_will_fail [2019/01/14 08:08] (current)
Hans Samios Resized image
Line 5: Line 5:
 We've all seen the behavior. We learned that we should provide "​ranges"​ of velocities when trying to forecast what is happening in the next Release. For a while we start out with good intentions. We use an average, and we use a "​recent"​ minimum and maximum to frame what might happen in the future. We've all seen the behavior. We learned that we should provide "​ranges"​ of velocities when trying to forecast what is happening in the next Release. For a while we start out with good intentions. We use an average, and we use a "​recent"​ minimum and maximum to frame what might happen in the future.
  
-{{ :​blog:​screen-shot-2015-08-17-at-2.33.41-pm.png?​nolink&​300 |}}+{{ :​blog:​screen-shot-2015-08-17-at-2.33.41-pm.png?​nolink&​600 |}}
  
 Then things change. We look at the "​minimum"​ number and say to ourselves "well that number really doesn'​t make sense because no one is expecting the team(s) to operate so poorly again."​ The same is true for the maximum number - no one believes it. We then decide that perhaps the average is the best indicator of what is going on. Then things change. We look at the "​minimum"​ number and say to ourselves "well that number really doesn'​t make sense because no one is expecting the team(s) to operate so poorly again."​ The same is true for the maximum number - no one believes it. We then decide that perhaps the average is the best indicator of what is going on.
  • /home/hpsamios/hanssamios.com/dokuwiki/data/pages/blog/why_a_plan_based_on_average_velocity_will_fail.txt
  • Last modified: 2019/01/14 08:08
  • by Hans Samios