Hmmmm. 1, 3, 5, 7, 11, 13, 17, 19, 23, 29, 31, 37 - etc. vs. 0, 1, 2, 3, 5, 8, 13, 21, 34 - etc. It's as valid as any other sizing scheme. I prefer Fibonacci simply because the displacement between the numbers grows as the amount of "unknown" in a task grows. With the primes, the displacement is: 2,2,2,4,2,4,2,4,6,2,6. Whereas with Fibonacci it's: 1,1,1,2,3,5,8,13,21. When numbers are too close together - especially with the task being relatively undefined, I find there can be a lot of quibbling about which side of the effort scale a task should fall on when in fact, in the end, it's a guess either way.

Of course!

Hi Chris. I'll post them tonight and put links to them in the blog post. They're visual presentations so hopefully they'll make sense (and they're kind of "big"). Once you get them, let me know if you have any questions.

Nicole,

Thanks for the note. I've been using AgileZen since the day it was released and have introduced it into the company as well. Lots of impressed people and its part of our Agile tool list for our clients. Separating the concepts of lean vs. my view of Agile is something I'm working on so hope to write a followup post soon.

Thanks,
Bill