This shows you the differences between two versions of the page.
|Both sides previous revisionPrevious revision|
|do_we_put_story_point_estimates_on_a_spike_enabler_story [2022/06/22 12:37] – hans||do_we_put_story_point_estimates_on_a_spike_enabler_story [2022/06/22 12:40] (current) – hans|
|Line 3:||Line 3:|
|> Yes. The basic rule is "if it takes capacity of the team to get the work done, then it should be visible in the Backlog and have an estimate."||> Yes. The basic rule is "if it takes capacity of the team to get the work done, then it should be visible in the Backlog and have an estimate."|
|-||Estimates and velocity help Teams to understanding of the capacity of the Team and reason about how much work a Team can take on. Further they provide Product Managers and Product Owners with the data needed to provide forecasts and roadmaps. In order to be used this way Team's need to ensure that anything that takes up capacity is represented in the Backlog so that:||+||Estimates and velocity help Teams to understand |
|- As work is completed, the capacity taken by that work is also captured in the form of velocity||- As work is completed, the capacity taken by that work is also captured in the form of velocity|
/home/hpsamios/hanssamios.com/dokuwiki/data/pages/do_we_put_story_point_estimates_on_a_spike_enabler_story.txt · Last modified: 2022/06/22 12:40 by hans