Differences

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

--- facilitation_-_play_pass_or_move [2018/06/19 19:40] – hpsamios
+++ facilitation_-_play_pass_or_move [2018/06/19 19:52] – hpsamios
@@ Line 5: / Line 5: @@
 ====== Premise ======
-The idea of "relative sizing" can be applied in a lot of situations. Most first learn of the concept in agile when we do estimates of the size of work. When agile Teams require an estimate of the work, they often use Story Points, a measure of relative size, as an estimate. We use Story Points because it is faster than estimation of absolute amounts. But the data that results is often more accurate as well. The idea that we can gauge something that is bigger or smaller than something we have, that we can do it quickly, and that we can turn these the result into numbers if required (through affinity mapping) is not limited to job size. We can apply the concept to estimates of relative business size, relative risk, relative impact, relative whatever.
+The idea of "relative sizing" can be applied in a lot of situations. Most first learn of the concept in agile when we do estimates of the size of work. When agile Teams require an estimate of the work, they often use Story Points, a measure of relative size, as an estimate. We use Story Points because it is faster than estimation of absolute amounts. And the data that results is often more accurate as well. The idea that we can gauge something that is bigger or smaller than something we have, that we can do it quickly, and that we can turn these the result into numbers if required (through affinity mapping) is not limited to job size. We can apply the concept to estimates of relative business size, relative risk, relative impact, relative whatever.
 Relative sizing also does not have to be done in a single dimension. For example, at the same time that we estimate relative risk, we can also estimate relative impact, if we set up both a horizontal and vertical axis. The technique can be applied as both a single and dual dimensions.
@@ Line 31: / Line 31: @@
   * Once the group places all the notes on the wall, they’ll continues to circulate through the line with Pass or Move options only
   * Once everyone in the line has passed on adjusting the relative size, the activity is over
-Optionally, add values between low and high using numbers in the Fibonacci sequence: 1,2,3,5,8,13, etc. This is done by affinity mapping clusters of items.
 If you want to do two variables, just create a horizontal and vertical axis. People place items of the wall commenting on both of these axis.
-Here is an example laying out business value (horizontal) and time criticality (vertical) from "low" (bottom left corner) to "high". In this case you can see that values have been assigned as well:
+Here is an example laying out probability of risk and impact:
-{{ :wiki:business_value_vs_time_criticality.png?600 |}}
+{{ :risk_probability_and_impact.jpg |}}
 ====== Ideas ======
@@ Line 46: / Line 44: @@
   * Have some fun with this - treat it as a conga line
   * If you have no numbers that are commonly known by the group, don't use numbers on the axis. Low / high, big / small etc are better labels and helps people focus relative sizing as opposed to trying to guess an absolute number.
+  * You can create values between low and high using numbers in the Fibonacci sequence: 1,2,3,5,8,13, etc. This is done by affinity mapping clusters of items.
+  * You can use circles to map out, for example, high risk or impact, and so show where you should focus first (see picture above)
 ====== What to Know More? ======