@@ -30,59 +30,58 @@ TL500 <!-- {.element: class="title-color"} -->
30
30
31
31
* A mechanism for sizing different work items * relative* to each other
32
32
* A tool to facilitate conversations, especially where there are different views on relative sizes
33
- * Common formats to call it : relative estimation, planning poker, count number of work items
33
+ * Other names you may have heard for this exercise : relative estimation, planning poker, counting the number of work items
34
34
35
35
36
36
37
37
#### _ Why use it?_
38
38
39
39
* Facilitates conversation
40
- * Helps align groups of people to reach consensus on their understanding regarding the size of complexity and/or value of an item
41
- * Avoids the emotion, buffering and other negative side effects of absolute estimation
40
+ * Helps align groups to reach consensus on their understanding regarding the size of, complexity, and/or value of an item
41
+ * Avoids the emotion, buffering, and other negative side effects of absolute estimation
42
42
43
43
44
44
45
45
#### _ How do we do it?_
46
- _ Things to consider before starting: _ <!-- {.element: style="font-size: smaller; font-weight: 100;"} -->
47
- * First we need to have done the product backlog refinement and the sprint planning
48
- * After we picked the user stories for the next sprint and put them into the Relative Estimation board
46
+ _ Things to consider before starting _ <!-- {.element: style="font-size: smaller; font-weight: 100;"} -->
47
+ * First, the product backlog refinement and the sprint planning must be done.
48
+ * Then, you pick up the user stories for the next sprint and put them into the Relative Estimation board.
49
49
50
50
51
51
52
52
#### _ How do we do it?_
53
- 1 . We draw a ladder and agree on the points we are going to use. A common practice is to use the Fibonacci series or T-Shirt sizes
53
+ 1 . Draw a ladder and agree on the points to use. A common practice is to use the Fibonacci series or T-Shirt sizes.
54
54
55
55
![ fibonacci-series] ( images/estimation/fibonacci-series.png ) <!-- {.element: class="" style="border:none; box-shadow:none; max-width:40%;" } -->
56
56
57
- 2 . Then we start the sizing for the stories: the first step is to identify the 1-pointer and the 13-pointer
58
- 3 . From there we then compare the other user stories to the previous items:
59
- - Maybe the second user story is a bit harder, so let's call that a 2-pointer
60
- - Then the next user story we need to ask ourselves how much harder or easier it is compared to the others
57
+ 2 . Then, begin sizing for the stories. The first step is to identify the 1-pointer and the 13-pointer.
58
+ 3 . Next, compare the other user stories to the previous items:
59
+ - Perhaps the second user story is a bit harder, so let's call that a 2-pointer
60
+ - Consider the story that follows. We must ask ourselves how much harder or easier it is compared to the others.
61
61
62
62
63
63
64
64
#### _ How do we do it?_
65
65
_ An example_ <!-- {.element: style="font-size: smaller; font-weight: 100;"} -->
66
- * 'Okay we have story A, is this bigger than the 3 points we have here?'
67
- * Assuming yes - 'Okay is it bigger than the 8 pointer? Or is it roughly the same size'
68
- * Assuming no - 'Okay so we'll say it is a 5 pointer then'
69
-
66
+ * 'Is Story A bigger than the 3 points we have here?'
67
+ * Assuming yes, ask "Is it bigger than the 8 pointer? Or is it roughly the same size?"
68
+ * Assuming no, "Okay, then let's say it is a 5 pointer."
70
69
71
70
72
71
### Exercise - Fruit Salad 🥗
73
72
#### _ Relative Estimation_
74
73
In 60 seconds ⏱...
75
74
76
- * Individually - write as many fruits as you can think of the wilder and weirder the better
75
+ * Individually, write down as many fruits as you can think of, the wilder and weirder the better.
77
76
78
77
79
78
80
79
### Exercise - Fruit Salad 🥗
81
80
#### _ Relative Estimation_
82
81
* As a Team
83
- * Move the fruit to one single list and remove duplicates
84
- * Create rows on a board and label them 1,2,3,5,8,13
85
- * Relative Estimate your fruit based in how hard is to peel and cut each fruit
82
+ * Combine the fruits into a single list and remove duplicates.
83
+ * Create rows on a board and label them 1, 2, 3, 5, 8, and 13.
84
+ * Perform a Relative Estimate of your fruits based on how hard is to peel and cut each fruit.
86
85
87
86
88
87
@@ -108,19 +107,19 @@ In 60 seconds ⏱...
108
107
109
108
#### Key Takeaways
110
109
</br >
111
- As we go through these estimations, conversations will occur within the team and you'll discover more with understandings beginning to align.
110
+ As we go through these estimations, conversations occur within the team and you'll discover more as understandings beginning to align.
112
111
113
- In this exercise this might include things like :
114
- - Perhaps someone has a tool that makes opening coconuts easier so maybe it doesn't require as much effort as we thought?
115
- - Maybe the orange has pips in it and also it's more difficult than the banana?
112
+ In this exercise these new discoveries might include things such as :
113
+ - Someone has a tool that makes opening coconuts easier, so perhaps it doesn't require as much effort as you first thought.
114
+ - The orange has pips in it and it's also more difficult to peel than the banana.
116
115
![ fruits] ( images/estimation/fruits.png ) <!-- {.element: class="" style="border:none; box-shadow:none; max-width:100%;" } -->
117
116
118
117
119
118
120
119
#### Facilitation Tips
121
- A helpful tool for big planning:
122
- * The relative estimation line is one technique that can help with this sort of thing allowing for quick and easy estimation based on past experience
123
- * It is important to avoid stories too big that are brought into the sprint and they are carried over multiple sprints. Because the story is never "done" the points cannot be cashed in.
120
+ A helpful tool for big planning
121
+ * The relative estimation line is a technique that helps planning by allowing for quick and easy estimation based on past experience.
122
+ * It is important to avoid stories that are too big and are carried over multiple sprints. Because the story is never "done", the points cannot be cashed in.
124
123
125
124
126
125
@@ -131,4 +130,4 @@ A helpful tool for big planning:
131
130
- [ T-shirt Sizing] ( https://openpracticelibrary.com/ )
132
131
- [ Planning Poker] ( https://openpracticelibrary.com// )
133
132
- [ Product Backlog Refinement ] ( https://openpracticelibrary.com/practice/backlog-refinement/ )
134
- - [ Acceptance Criteria ] ( https://openpracticelibrary.com/ )
133
+ - [ Acceptance Criteria ] ( https://openpracticelibrary.com/ )
0 commit comments