Differences

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

--- what_can_we_do_to_improve_our_point_based_estimates [2019/01/09 14:14] – Refactored to just focus on "improvement" hpsamios
+++ what_can_we_do_to_improve_our_point_based_estimates [2020/06/02 14:21] – external edit 127.0.0.1
@@ Line 7: / Line 7: @@
 For many organizations, we focus on making Story Points a true measure of the relative size of the work, and velocity as the true capacity of the team to complete requirements to done.
-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 up the each Team estimates of User Stories that are Done in a Sprint / Iteration.
+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:
@@ Line 37: / Line 37: @@
   * [[Track Found Work Metric]]
   * [[Use Ranges to Understand Risk]]
+====== Want to Know More? ======
+  * [[how_do_we_use_points_to_estimate_work|How Do We Use Points to Estimate?]]
 {{tag>Team Estimates Forecast FAQ Points Improve}}