Fed up with constantly trying to digest story points and their stifling ineffectiveness? There’s another way! — When determining how big a piece of work is, it is common to use story points, often assigned to backlog items using a method called “Planning Poker”. Typically, the story points aim to indicate effort or even just complexity (depending on who you ask!), and provide a very useful abstraction…

And why I stopped calling them all User Stories — The term “user story” has become synonymous with the product backlog item. You’ve quite likely seen user stories that state something like “as a developer I want to see error logs so that I can fix bugs” or similar. …