1. relative sizing

2. What is the challenge with absolute estimates?
Relative sizes involve the whole team - encourages collaboration and growth
Absolute sizes are typically done by the person doing the work
Absolute sizes breed unrealistic accountability
Relative sizes keep the focus on team velocity
Absolute sizes tend to be inflated when the pressure is on to deliver
Relative sizes remain constant over time
Absolute sizes take a long time with lots of debate
Relative sizes are much quicker and surprisingly accurate
Estimated hours vs. actual hours create all kinds of stress that is unproductive
Actual size also encourages comparisons between teams – why does one team of 5 people do 40 pts and another team only 37?

3. let’s try it!!!

10. what challenges do you see?

11. Guidance for Planning Poker
1. Choose the smallest story you would normally do and call it a “1”
2. PO reads the next item
3. Team estimates item’s size, relative to previous items
4. If no consensus, Discuss 60 seconds, Goto step 3
5. If no consensus after 3 votes, run consent check on largest estimate, so we can move on. Go to Step 2
6. Repeat until timebox is done
Relative Estimating approach.
Use Story Points. No units. Relative measure of “Bigness”.
ATC Scale:
1 :: Really Small
2 :: 1 Day (Done Done)
3 :: 1-2 days
5 :: 2-3 days
8 :: 4-7 days
13 :: Too big for a 2-week sprint