> Now let me summarize and you can decide if we have the same understanding of user stories here: A user story describes a work item. It puts extra emphasis on

> Now let me summarize and you can decide if we have the same understanding of user stories here: A user story describes a work item. It puts extra emphasis on understanding your users and why satisfying their needs is valuable to them. I don't think a user story should describe a work item. A user story may entail multiple work items, or a single work item may fulfill multiple users stories. A description of a user need is what they are. Their relationship to features is not simple. I agree that most of their value is in deciding if you actually built something to address all your important user stories, but of course you can only really do that by asking users. They are useful for organizing your thinking about what you need to build, though, so I imagine that is how they get conflated with work items or features. I hate personas. At my current company, we have dozens of them, and nobody ever uses them or refers to them. A major effort to create, and time wasted as far as I'm concerned. At a previous company, we had zero personas, but we did have a list of actual, real people who represented the kinds of users we targeted, and we would meet with them to identify new features and validate our designs and prototypes. That was approximately one million times more effective than a list of made-up personas. You cannot hope to capture the complexity of a real person's real needs in an artificial persona.