User Stories describe software features concisely, eg.
As a Customer,
I want to change my billing address,
So that I am charged correctly for shipping
This format leads to concise stories:
As a [user role],
I want to do [action],
So that [reason]
Here's how we work with the User Stories:
User Stories are the building blocks of the Agile process. Each User Story is a small independent task that adds value to a project. They offer a simple and flexible alternative to traditional requirements gathering. User Stories are intentionally short on detail. This allows us to defer lots of decision-making until we're ready to actually do the work and our collective knowledge of the project is much greater. At that point, the decisions we make about the project will be much more accurate. Agile acknowledges the fact that it's usually not practical to know everything about a project before you've even started it! We suggest this three-part format for User Stories: