what_can_we_do_to_improve_our_point_based_estimates
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
what_can_we_do_to_improve_our_point_based_estimates [2019/01/09 14:41] – hpsamios | what_can_we_do_to_improve_our_point_based_estimates [2019/01/14 06:17] – [Backgound] hpsamios | ||
---|---|---|---|
Line 7: | Line 7: | ||
For many organizations, | For many organizations, | ||
- | Most organizations settle on a team-by-team Story Point based approach to estimate work. These estimates are used to understand how much the team can deliver in a Sprint / Iteration. The capacity to deliver working code, called the Team Velocity is determined by summing | + | Most organizations settle on a team-by-team Story Point based approach to estimate work. These estimates are used to understand how much the team can deliver in a Sprint / Iteration. The capacity to deliver working code, called the Team Velocity is determined by summing the Team estimates of User Stories that are Done in a Sprint / Iteration. |
We come to rely on this information for a number of uses. For example it helps us plan and understand how Teams are doing. A number of Teams have reported issues in both calculating and using Story Points. The following approaches were pulled together from 2 primary sources: | We come to rely on this information for a number of uses. For example it helps us plan and understand how Teams are doing. A number of Teams have reported issues in both calculating and using Story Points. The following approaches were pulled together from 2 primary sources: |
/home/hpsamios/hanssamios.com/dokuwiki/data/pages/what_can_we_do_to_improve_our_point_based_estimates.txt · Last modified: 2022/02/23 06:59 by hans