Work Management

Story Points

Story points explained: what they measure, why teams size effort not hours, the Fibonacci scale, planning poker and how velocity turns points into a forecast.

  • 8 min read
  • 5 questions
  • +35 XP
Transcript

Story Points Explained by Cats Planning poker begins. Cards are out. Cats are ready. Kitty joins the circle. Boss cat drops a user story. “How many points?” Instant panic. One cat throws a “3.” Another slaps down a “13.” A third shows a card with a fish drawn on it.

Not helpful. So Kitty learns: Story points aren’t hours. They’re not days. They measure effort, complexity, and uncertainty. Simple task? Few surprises? 2 points. Tricky logic? Some unknowns? 5 or 8. Something cursed? Legacy code? 13. Always 13. Planning poker continues.

Cats throw cards like they’re reading tarot: “I sense hidden bugs.” “I foresee API sadness.” “I feel… an existential dread in this one.” Eventually, the team aligns. Not perfectly. But collectively. And that’s the real magic: Story points don’t measure time.

they measure shared pain. A system where cats rarely agree, always learn, and somehow get better at predicting the future… even though no cat knows what a point actually means.