User Story vs Project Requirements
People think a user story is a requirement in a new format. A requirement tries to write down all the detail up front. A user story is a short note that promises a talk. The detail comes later, in that talk and in the acceptance criteria.
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.
Project Requirements
The needs a project's result must meet. Each one is written down and checked.
Requirements are the needs a project's result must meet. They come from the people who will use it, pay for it or run it. Some say what the result must do, like "send a receipt". Others say how well, like "load in two seconds". The team gathers them, writes them down and checks them with the people who asked.
In one line
- User Story
- A short note of one thing a user wants, and why. The details come from talking.
- Project Requirements
- The needs a project's result must meet. Each one is written down and checked.