detailing features and then the features were completely changed by the time they were implemented Anecdote: project estimation took 6 months, flip-flopping between solutions and estimating all possibilities, then took 1 year to develop
anchoring. (Can’t estimate in isolation). Fibonacci removes some options so at higher levels, forced to consider the complexity up or down (if it was going to take a 6, it’s probably an 8) It’s still numbers, so team needs to decide what they mean. What is a point?
into numbers, so it might as well be you. Sure we can measure the velocity of cards, but then we have to break them down anyway. How many smalls equal a large? We did 2 mediums and a large this week but 4 smalls and a medium the previous week.
you finished = that’s your velocity no need to do formal estimation, just break cards down like you normally would with tasks takes a few sprints to get decent velocity numbers and would still require some way of breaking cards down in the backlog. Could work well with tshirt/ reptile size estimates.