"Should we use story points for...?": The wrong question.

May 22, 2022
Getting a useful answer depends on knowing the right question to ask.

“Should you story-point bugs or spikes?”

This question never dies. I see it asked all the time. Maybe it’s one you’ve asked.

But I’m not going to answer it today.

Instead, I’m going to try to kill the question itself.

Of course, there are many reasons you definitely should use story points for bugs and spikes. There are also just as many reasons you definitely should not.

And that’s the catch: What you should do depends on your goal! What problem are you trying to solve?

Why are you using story points? Answer that question first. Then it should be obvious whether or not it makes sense to use story points for bugs or spikes.

And if you can’t answer that question, then you probably shouldn’t be using story points at all. Which also answers the original question! 😀

Related Content

Velocity, capacity, and unplanned work

Velocity usually includes unplanned work, which limits its usefulness for capacity planning and forecasting.

Story Points means Relative Estimation, right? Not so fast.

Relative Estimation is possible in any unit, including time. And absolute estimation is also possible in any unit, including story points.

Rose bushes and story points

Gardening with a 1-year old takes a lot longer. How should this affect our estimates?