Estimating story points can be a tedious process. So tedious in fact that some teams abandon doing story points to help predict their velocity. Instead of letting go of this valid way to predict upcoming work, how about finding a way to make the process of estimating points much faster? Not only faster, but FUN! Yes, story point estimation and fun in the same paragraph!
While there are many methods that use stories as a means for prioritizing development, there's a basic divide that asks whether it should be done with numbers or without. There are arguments on both sides, but instead of examining these, people tend to fall into one side naturally. Once there, they can become quickly entrenched in the belief that the other camp is foolishly mistaken.