Standard Spin on Story Points
There are a lot of good videos and articles out there about Story Points. They describe in various ways, what the presenter thinks story points are, what they’re good for, and how they’re used. I do not want to repeat that information here, too much. It’s all good stuff, but it always left me hanging.
Sure, I get that Story Points are for mid-range to long-range planning. I get that sizing is needed in the earliest stages of planning, and using “ideal hours” is impractical if not impossible until later, during iteration planning, when architects and engineers can decompose the problem at hand into measurable morsels of work. I get it.
Several things remained fuzzy for me, though, including the following:
- How does a team start sizing with abstract story points?
- How does the suggestion that they use the Fibonacci series for weighting the relative size or difficulty really work?