Differences

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

--- how_do_i_convert_points_and_velocity_to_dollars [2020/06/04 11:17] – Removed LINKBACK hans
+++ how_do_i_convert_points_and_velocity_to_dollars [2020/06/10 12:44] (current) – ↷ Links adapted because of a move operation hans
@@ Line 30: / Line 30: @@
   * Does not require additional reporting (“oh the UI is so simple everyone can do it” is just another road bump for people who should be focusing on producing value)
-In reality, if the work is large enough you’ll find an close enough approximation by simply counting the number of user stories in an epic as you do the work and proportioning the cost of the team that way (law of large numbers takes over - see [[blog:do_we_need_points_to_generate_a_release_burn-up_chart|Do We Need Points To Generate a Release Burn-up Chart?]] for more on this thinking). In the same way I expect you’ll eventually find that if you do to proportioning of cost via hours, you end up with pretty close to the same result as points. Many argue that ratios of points produce a better result than hours since it is more complete and both the people doing the work and the managers of that work talk about the same thing.
+In reality, if the work is large enough you’ll find an close enough approximation by simply counting the number of user stories in an epic as you do the work and proportioning the cost of the team that way (law of large numbers takes over - see [[do_we_need_points_to_generate_a_release_burn-up_chart|Do We Need Points To Generate a Release Burn-up Chart?]] for more on this thinking). In the same way I expect you’ll eventually find that if you do to proportioning of cost via hours, you end up with pretty close to the same result as points. Many argue that ratios of points produce a better result than hours since it is more complete and both the people doing the work and the managers of that work talk about the same thing.
 You can also come up with a "cost / point" calculation based on team velocity and cost (eg For a quarter, divide the total cost of the team by the total points completed by the team, (including Product Owner, Scrum Master, team members and the appropriate percentage of part-time contributor salaries). You now have the “cost per point”). Some will find this useful for looking ahead when estimates are required for projects, for example.