User Scenario vs User Story
People think a user scenario is a user story, and it is not. A user story is one small thing to build, in one line: as a user, I want this, so that I can do that. A user scenario is a longer story about a real moment, with where the person is and what gets in the way. Designers write scenarios to understand people. Teams write stories to plan the work.
User Scenario
One person, one product and one goal, told as a short story.
A user scenario is a short story about a person using a product to reach a goal. It says who they are, where they are, what they want and what gets in the way. It is written before the design, so the team designs for a real moment. A scenario often stars a user persona. It keeps the team thinking about the whole situation, not just a screen.
User Story
A short note of one thing a user wants, and why. The details come from talking.
A user story is a short note about one thing a user wants. It is written from the user's side, in plain words. The usual form is: as a kind of user, I want something, so that I get a gain. The card is kept short on purpose. The details come from talking with the team and from the acceptance criteria. A story should be small enough to finish in one sprint.
In one line
- User Scenario
- One person, one product and one goal, told as a short story.
- User Story
- A short note of one thing a user wants, and why. The details come from talking.
These live in different corners of the glossary (Design and Business), which is exactly why they get confused.