Posted By Ian Mitchell on 19 Nov 2013 06:26 AM
>> 3. How do I transfer that idea to the team?
> 3. Focus on relative sizing of effort. We are bad at predicting
> how many hours something we will take. We are (relatively)
> better at estimating that one task will take longer than another.
To do this, try playing "the estimation game", or team sorting as it is sometimes called. It discourages team members from trying to over-analyze the numbers. You can start off using t-shirt sizes and map points to them later.
thanks for all your replies. I haven't figured out the intention of the "number of solved problems" idea yet and I was glad to see, that you didn't understand it as well.
I had quite a good magic estimation with "level of understanding". I used a custom scale like "could start immediately", "one tiny question" .... "give me 10 minutes with the po" and "WTF" and felt that the team could identify themselves with it.
Since the PO tried to get the remaining questions answered almost all of the stories were set to "could start immediately" which in my pov killed the idea of having useful story points afterwards. Now we're in a sprint with only "level of understanding" and I have some doubts on how to calculate the velocity. But I could assign fibonacci numbers to my scale, I assume.
Because of this I will use "level of understanding" only as additional attribute of a story and will try to focus on shirt sizes in the next meeting. I think this complies with your suggestion for focus on relative sizing. Do you think that this is a feasible solution?