Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
establish_points_guidelines_for_each_point_value [2016/06/16 09:33]
hpsamios
establish_points_guidelines_for_each_point_value [2016/07/03 13:38] (current)
Line 6: Line 6:
 To set this up, work with the team to create definitions that everyone can agree on. For example, the team might have found that a small GUI change with no new business object is something they consider to be a 3, whereas something with a large GUI change might start of by being an 8, with 13 being used if it also means a new business object is required as well. To set this up, work with the team to create definitions that everyone can agree on. For example, the team might have found that a small GUI change with no new business object is something they consider to be a 3, whereas something with a large GUI change might start of by being an 8, with 13 being used if it also means a new business object is required as well.
  
-Teams have found this helps stabilize the Actual Velocity, helps show when the Scrum Team is improving, or not, and generally provides more confidence for the estimates. It works in conjunction with [[establish_a_keystone_story|Establish a Keystone User Story]]+Teams have found this helps stabilize the Actual Velocity, helps show when the Scrum Team is improving, or not, and generally provides more confidence for the estimates. It works in conjunction with [[establish_a_keystone_story|Establish a Keystone User Story]]. To help he team figure out things like complexity you could look to [[establish_a_things_that_matter_matrix|Establish a "​Things That Matter"​ Matrix]]
  
 ~~LINKBACK~~ ~~LINKBACK~~
  • /home/hpsamios/hanssamios.com/dokuwiki/data/pages/establish_points_guidelines_for_each_point_value.txt
  • Last modified: 2016/07/03 13:38
  • (external edit)